WEBVTT Kind: captions; Language: en

00:00:17.000 --> 00:00:20.000
I'm going to give it just one more
minute before we get started.

00:00:22.000 --> 00:00:25.001
But while you wait,
will you please drop in the chat

00:00:25.001 --> 00:00:27.001
where you're zooming in from?

00:00:27.001 --> 00:00:30.000
We'd love to see where everyone's coming from.

00:00:30.001 --> 00:00:37.000
And it just, I don't know,
fills me with awe that people are coming from

00:00:37.000 --> 00:00:40.000
Warsaw where it's 1 a.m.
and Lisbon where it's midnight.

00:00:41.001 --> 00:00:42.001
Thank you so much.

00:00:50.000 --> 00:00:54.001
Well it is exactly five o'clock,
so I think we're going to get started.

00:00:54.001 --> 00:00:59.001
Welcome, welcome everyone to Centering Respect,
Trust, and Equity in the D-Web.

00:01:00.000 --> 00:01:02.000
This is our November D-Web meetup.

00:01:02.000 --> 00:01:03.000
I'm Wendy Hanamura.

00:01:03.001 --> 00:01:05.000
I'm going to be your host for today.

00:01:05.000 --> 00:01:09.000
I'm also the Director of Partnerships
at the Internet Archive and one of the

00:01:09.000 --> 00:01:13.000
many, many people stewarding
this community called the D-Web.

00:01:13.001 --> 00:01:18.000
I am coming to you from San Francisco,
California, and I want to ask you to do me

00:01:18.000 --> 00:01:21.000
a favor and drop in the name
of the city where you are

00:01:21.000 --> 00:01:23.000
zooming in from in the chat.

00:01:23.000 --> 00:01:25.000
We'd love to see where people are.

00:01:25.001 --> 00:01:31.001
I see Nate in New York and yes,
Ayal in Warsaw and Savannah in

00:01:31.001 --> 00:01:33.000
Lisbon and Jenny in Oakland.

00:01:34.000 --> 00:01:35.001
Thank you so much for joining us.

00:01:36.000 --> 00:01:40.001
I know that it is very early morning
for the folks in Asia and very late

00:01:40.001 --> 00:01:42.001
in the middle of the night for those in Europe.

00:01:43.000 --> 00:01:46.000
So we really appreciate you
making it to this virtual meetup.

00:01:47.000 --> 00:01:50.000
We want to start this meetup
by thinking about some of the

00:01:50.000 --> 00:01:51.001
biggest questions out there.

00:01:52.000 --> 00:01:56.001
How do we embody the values we
hold dear in this new tech world?

00:01:57.000 --> 00:02:01.000
I want to remind you of the
principles of the D-Web that were

00:02:01.000 --> 00:02:02.001
created by our whole community.

00:02:04.000 --> 00:02:08.000
We're going to drop a link to
those principles in the chat.

00:02:08.001 --> 00:02:11.000
And the third principle, mutual respect.

00:02:11.001 --> 00:02:15.000
That's what our featured speaker
today is going to explore.

00:02:15.001 --> 00:02:18.001
How do we build a more
ethical decentralized web?

00:02:19.000 --> 00:02:23.001
How do we build a web that's centered
on respect, on trust, on equity?

00:02:24.001 --> 00:02:28.001
First, I want to share with you a little
bit about the game plan for this event.

00:02:29.001 --> 00:02:33.001
You're going to hear our featured speaker,
Coraline Ada-Empi,

00:02:33.001 --> 00:02:35.001
speak about those topics.

00:02:36.001 --> 00:02:41.000
Then we're going to take you kind of around
the world with seven lightning talks

00:02:41.000 --> 00:02:44.001
by leaders in different
decentralized tech projects.

00:02:45.000 --> 00:02:50.001
Finally, as we always do, we'll end up in
Gather Town, which is a place where you

00:02:50.001 --> 00:02:53.000
can roam around, meet people, socialize.

00:02:53.001 --> 00:02:56.001
It's virtual, but it's as close
as you can get to networking and

00:02:56.001 --> 00:02:58.001
socializing in the D-Web.

00:02:59.001 --> 00:03:02.001
By now, you're all Zoom experts, I know.

00:03:03.000 --> 00:03:04.000
But just a few tips.

00:03:04.001 --> 00:03:05.001
Please keep yourself on mute.

00:03:07.000 --> 00:03:10.001
It will probably be best for
you if you hit speaker view.

00:03:10.001 --> 00:03:12.001
And if you have a question for our

00:03:12.001 --> 00:03:14.000
speakers,
we'll try and save a little bit of time.

00:03:14.000 --> 00:03:15.001
And you can raise your hand.

00:03:16.000 --> 00:03:18.000
And I'll try to get to as
many of you as possible.

00:03:19.000 --> 00:03:22.000
We also want you to make
yourself heard in the chat.

00:03:22.001 --> 00:03:25.000
Everybody reads the comments, the observations.

00:03:25.000 --> 00:03:28.000
You will often find people
answering your questions.

00:03:28.000 --> 00:03:30.000
So please put those in the chat.

00:03:30.001 --> 00:03:33.001
And I also want to remind
you of our code of conduct.

00:03:34.000 --> 00:03:38.001
This is always a lively gathering,
but it has always been a respectful gathering.

00:03:39.000 --> 00:03:41.001
We do not tolerate any forms of harassment.

00:03:42.000 --> 00:03:46.000
If you have some, please know that
there are moderators standing by.

00:03:46.000 --> 00:03:51.001
And you can always email us at ethics at
archive.org to let us know later about

00:03:51.001 --> 00:03:54.000
something that you wanted
to raise a concern about.

00:03:55.001 --> 00:04:01.001
But first, it's my pleasure,
my honor to introduce to you Coraline Ada Emke.

00:04:02.000 --> 00:04:06.000
She's a leader and a pioneer in
creating the contributor covenant.

00:04:07.000 --> 00:04:10.001
A terrific code of conduct
for open source communities.

00:04:11.000 --> 00:04:16.000
She's also the leader and founder of the
ethical source movement and the ED of

00:04:16.000 --> 00:04:20.000
the brand new organization for ethical source,
which I just learned started

00:04:20.000 --> 00:04:21.001
in January of this year.

00:04:22.001 --> 00:04:28.000
You may know Coraline because she also
wrote the very powerful essay, The Sacred

00:04:28.000 --> 00:04:32.000
Geometry of Respect, Trust and Equity
for the Internet Archive and the D-Web,

00:04:32.001 --> 00:04:34.001
where she suggests a new way forward.

00:04:35.001 --> 00:04:39.000
We're honored to have Coraline
share her insights into how

00:04:39.000 --> 00:04:40.001
to build a more ethical D-Web.

00:04:41.000 --> 00:04:43.000
Please welcome Coraline Ada Emke.

00:04:44.000 --> 00:04:47.001
Wendy, thank you so much for
that very kind introduction.

00:04:47.001 --> 00:04:51.000
And I want to say I'm very I
was very honored to be asked

00:04:51.000 --> 00:04:52.001
to write about that D-Web principle.

00:04:52.001 --> 00:04:55.001
It's something that I that's very
near and dear to my heart and very

00:04:55.001 --> 00:04:57.000
near and dear to the work that I've been doing.

00:04:58.001 --> 00:05:02.000
And I'm also honored to be able to
present here today to everyone.

00:05:03.000 --> 00:05:08.001
So by way of introduction as a as an append
to Wendy's wonderful introduction, I

00:05:08.001 --> 00:05:12.000
began my career as a software developer,
as a software engineer.

00:05:13.000 --> 00:05:18.000
I have a twenty seven year career
in software development, 16

00:05:18.000 --> 00:05:19.001
years in the open source community.

00:05:20.001 --> 00:05:24.000
When you mentioned Contributor Covenant,
it was actually the first and remains

00:05:24.000 --> 00:05:26.001
the most popular kind of conduct
for open source communities.

00:05:27.000 --> 00:05:30.000
So you could say I invented Codeofconduct.
markdown.

00:05:30.001 --> 00:05:36.001
In 2018, I was invited to speak at the
United Nations on the on the topic of

00:05:36.001 --> 00:05:38.001
human rights abuses by tech corporations.

00:05:39.001 --> 00:05:45.001
In 2019, I created the Hippocratic License
and the Hippocratic License 3.0 just

00:05:45.001 --> 00:05:47.001
came out last last month.

00:05:47.001 --> 00:05:51.001
And it's an open source license
intended to protect universal

00:05:51.001 --> 00:05:53.001
principles of human rights.

00:05:54.001 --> 00:05:58.001
And ethical source,
the Organization for Ethical Source, as you

00:05:58.001 --> 00:06:00.001
mentioned, was founded this year.

00:06:00.001 --> 00:06:03.000
And I invite you all to go to ethicalsource.
dev.

00:06:03.001 --> 00:06:08.000
And also in particular, ethicalsource.
dev slash principles for the ethical source

00:06:08.000 --> 00:06:10.000
principles, which I was so pleased to see.

00:06:10.000 --> 00:06:15.001
We're actually referenced as related
efforts on the on the web principles page.

00:06:16.001 --> 00:06:18.000
So I'm going to jump right in. I don't have any

00:06:18.000 --> 00:06:20.000
slides. I'm just going to talk with you all.

00:06:20.001 --> 00:06:25.000
So I want to start by by calling
back to the open definition.

00:06:25.000 --> 00:06:30.000
The open definition, which was written in 2005,
reads that open means anyone can

00:06:30.000 --> 00:06:35.001
freely access, use, modify and share
for any purpose subject to the most

00:06:35.001 --> 00:06:39.000
requirements that preserve
provenance and openness.

00:06:40.000 --> 00:06:45.000
And what I one thing that strikes me about
the the open definition and the sphere

00:06:45.000 --> 00:06:47.001
that I work in,
the open source definition, is that

00:06:47.001 --> 00:06:49.000
they're very licensed focused.

00:06:49.001 --> 00:06:54.001
They're very they're they discuss legal
and technical considerations, which I

00:06:54.001 --> 00:07:01.000
think in in the world today ignores
the very real human context of the

00:07:01.000 --> 00:07:03.001
technologies we create and
the content we create.

00:07:05.000 --> 00:07:08.001
And then the same way that the open source
definition really doesn't reflect the

00:07:08.001 --> 00:07:11.000
practice and the experience of open source.

00:07:11.000 --> 00:07:12.000
This is legal to mention.

00:07:12.001 --> 00:07:17.001
I fear that the the open definition has
that same kind of weakness and requires

00:07:17.001 --> 00:07:22.001
that same kind of iteration because
it fails to consider the widespread

00:07:22.001 --> 00:07:26.000
disparities in access and
opportunity and representation.

00:07:27.000 --> 00:07:32.001
It fails to consider outcomes, asking the
question, how can open be used to cause

00:07:32.001 --> 00:07:37.001
harm, who is impacted and fundamentally
to whom are we extending rights?

00:07:39.000 --> 00:07:44.000
In short, our definition of open to date
fails to acknowledge systems of power

00:07:44.000 --> 00:07:45.001
and systems of oppression.

00:07:46.000 --> 00:07:49.001
But I'm very happy to see over the past
couple of years, there's something big

00:07:49.001 --> 00:07:53.001
happening across the broader digital
rights ecosystem and the D web

00:07:53.001 --> 00:07:55.000
principles are part of it.

00:07:55.001 --> 00:07:59.001
The D web, the preamble to the principles
say that the principles define the

00:07:59.001 --> 00:08:05.000
values of a decentralized web based
on enabling agency of all peoples.

00:08:05.001 --> 00:08:09.001
And it's the basis for behavioral norms
and importantly mutual accountability.

00:08:10.001 --> 00:08:14.000
And in this way, it looks beyond mere openness,
which is critical.

00:08:15.000 --> 00:08:19.001
And the D web principles reflect an
evolution of our understanding of what open

00:08:19.001 --> 00:08:22.000
means and they're part of a
change we're starting to see much

00:08:22.000 --> 00:08:24.000
more broadly and we'll come back to that.

00:08:24.001 --> 00:08:28.000
But first, let's explore the D
web principle of mutual respect.

00:08:28.001 --> 00:08:32.000
The principle of mutual respect
is broken into three components.

00:08:32.001 --> 00:08:36.001
The first being primarily around codes
of conduct, the second, acting out of

00:08:36.001 --> 00:08:40.001
respect for others and the third one,
practices and governance that pursue

00:08:40.001 --> 00:08:43.000
equity, mutual trust and respect.

00:08:43.000 --> 00:08:48.001
And when I was first invited to write
about this principle, my fear was That I

00:08:48.001 --> 00:08:53.000
was expected to write 1500 words on a code
of conduct and that's not really what

00:08:53.000 --> 00:08:57.001
I wanted to do. What grabbed me were
those last three terms and that third

00:08:57.001 --> 00:09:01.001
bullet,
the pursuit of respect mutual trust and equity.

00:09:02.000 --> 00:09:06.001
And the writing prompt I was given was
how does this principle point to us point

00:09:06.001 --> 00:09:08.001
us toward building better technology.

00:09:09.001 --> 00:09:13.001
And I realized that better is doing a lot
of work in that sentence and it raises

00:09:13.001 --> 00:09:18.000
questions for me like how do we define better?
How do we measure better? What

00:09:18.000 --> 00:09:20.001
does it really mean in practice?
And those are the questions

00:09:20.001 --> 00:09:22.001
that I tried to address in my piece.

00:09:23.001 --> 00:09:29.000
So to start with, let's look at respect.
Fostering a culture of mutual respect

00:09:29.000 --> 00:09:33.001
starts with making our values and
making our social contracts explicit.

00:09:33.001 --> 00:09:38.001
Continually reassessing their impact
and evolving them over time, we address

00:09:38.001 --> 00:09:41.000
changes within our community
and within the world at large.

00:09:42.001 --> 00:09:47.001
And this respect is of course extended to
our collaborators and that manifests as

00:09:47.001 --> 00:09:51.001
things like codes of conduct,
transparent and representative governance.

00:09:52.000 --> 00:09:57.000
We also focus on the needs of our users
and our adopters and that influences the

00:09:57.000 --> 00:10:02.000
ethical decisions that inform our
ergonomics and also involves our licensing,

00:10:02.001 --> 00:10:04.000
which of course is a component of open.

00:10:05.000 --> 00:10:09.000
But as there's a third component,
there's a third aspect of respect that I've

00:10:09.000 --> 00:10:13.000
been talking about recently,
and that is respect for collateral users.

00:10:13.001 --> 00:10:17.000
In the open source world and in the
technology world in general, a collateral

00:10:17.000 --> 00:10:23.001
user we define as someone upon whom a
technology is used, often without their

00:10:23.001 --> 00:10:30.000
consent. Now, Contributor Covenant,
when I created that, that was about being

00:10:30.000 --> 00:10:32.001
respectful to within our communities.

00:10:34.001 --> 00:10:40.000
And recently we had an issue,
or rather a pull request, open on the

00:10:40.000 --> 00:10:41.001
Contributor Covenant repository.

00:10:42.001 --> 00:10:47.000
And the author of the pull request said,
being, took issue with the statement,

00:10:47.001 --> 00:10:50.001
being respectful of differing opinions,
viewpoints and experiences.

00:10:51.001 --> 00:10:55.000
And he claimed that respect can't
be mandated and that rather

00:10:55.000 --> 00:10:57.000
we should focus on tolerance.

00:10:57.001 --> 00:11:02.000
And I think there's a huge difference
between tolerance and respect.

00:11:03.000 --> 00:11:07.001
And so, as part of my research for the piece,
I found a journal article was

00:11:07.001 --> 00:11:10.001
published in Perspectives on
Psychological Science just last year.

00:11:11.000 --> 00:11:15.001
And the paper was called the negative
implications of being tolerated, tolerance

00:11:15.001 --> 00:11:17.000
from the target's perspective.

00:11:18.000 --> 00:11:24.000
And there were some really good, some
really salient points that were made in the

00:11:24.000 --> 00:11:29.000
paper, and it was actually sort of a
meta-analysis and they indicated that mere

00:11:29.000 --> 00:11:34.000
tolerance actually has a significant
negative effect on the health and well-being

00:11:34.000 --> 00:11:38.001
of those who are being tolerated.
Not just emotional health, not only mental

00:11:38.001 --> 00:11:40.000
health, but also physical health.

00:11:41.000 --> 00:11:44.001
And when you think about tolerance,
think about the things you say you tolerate.

00:11:45.001 --> 00:11:49.001
We tolerate things that we don't like.
We tolerate a headache. We tolerate a

00:11:49.001 --> 00:11:53.001
boring party.
We tolerate a tedious but necessary task.

00:11:54.001 --> 00:11:59.000
So tolerance is really being in spite
of ourselves enduring something that we

00:11:59.000 --> 00:12:04.000
don't enjoy. And that's not what I want.
I don't want to be tolerated. And to the

00:12:04.000 --> 00:12:09.001
research that I read really put words,
something that I myself have experienced

00:12:09.001 --> 00:12:15.000
as a transgender woman, how tolerance of
someone who's transgender manifests is

00:12:15.000 --> 00:12:20.001
this begrudging fine, I'll use your pronouns
and I'll keep my opinions to myself

00:12:20.001 --> 00:12:26.000
versus respect, which says I value you,
not in spite of who you are, but

00:12:26.000 --> 00:12:27.001
because of who you are.

00:12:28.001 --> 00:12:33.001
And I wrote in the piece, tolerance is
the privilege of the powerful. It is a

00:12:33.001 --> 00:12:36.001
granting of permission to deviate
from the norms of the majority.

00:12:37.001 --> 00:12:42.000
And with it comes the implicit threat that
this permission can be revoked at any

00:12:42.000 --> 00:12:49.000
time. Tolerance centers the comfort of
the majority and asking the powerless to

00:12:49.000 --> 00:12:53.000
be tolerant is asking them
to endure their oppression.

00:12:55.000 --> 00:13:00.000
The second point was about mutual trust.
And I opened with a quote, without

00:13:00.000 --> 00:13:04.001
trust, conflict is politics.
With trust, conflict is a pursuit of truth.

00:13:05.001 --> 00:13:09.001
And I explained that there are two trust
metals that are recognized by social

00:13:09.001 --> 00:13:13.000
scientists. The first being transactional
and second being effective.

00:13:13.001 --> 00:13:19.001
And transactional trust is very prominent
in the white West, in Western Europe

00:13:19.001 --> 00:13:24.001
and North America. It's very transactional.
This is the kind of trust that is

00:13:24.001 --> 00:13:27.001
earned by consistently delivering a result.

00:13:28.000 --> 00:13:32.001
So we might trust someone in an open source
community for consistently delivering

00:13:32.001 --> 00:13:37.001
quality code. But it's important to recognize,
especially with a global scope of

00:13:37.001 --> 00:13:42.001
what we do, that there are other trust
metals and that the transactional trust

00:13:42.001 --> 00:13:44.001
model, in fact, is not universal.

00:13:45.001 --> 00:13:49.001
And then a lot of other parts of the world,
effective trust is more prevalent.

00:13:50.000 --> 00:13:55.000
And effective trust is more relational.
It's more community oriented. And I think

00:13:55.000 --> 00:13:59.001
most importantly, it's focused on what happens,
not what you're trying to do.

00:14:00.001 --> 00:14:07.001
And trust is a very complicated concept,
of course. And we can

00:14:07.001 --> 00:14:12.001
think about trust again in the context
of power imbalances or power systems.

00:14:13.000 --> 00:14:18.000
It's necessary for us to bridge these two
different trust models. Because if we

00:14:18.000 --> 00:14:23.000
only focus on transactional trust,
that leads us down a slippery slope toward

00:14:23.000 --> 00:14:30.000
digital colonization. So what we have
to do as people with privilege, as

00:14:30.000 --> 00:14:35.001
people with influence, is earn that trust.
We can't assume that simply because we

00:14:35.001 --> 00:14:39.001
have an institution and we give ourselves
authority that we will be respected.

00:14:40.000 --> 00:14:46.000
We're respected not because of our intent,
but because of our impact. And as I

00:14:46.000 --> 00:14:49.001
learned as part of my work in the social
justice and tech movement in the 20

00:14:49.001 --> 00:14:52.001
-teens, we had a saying, intent is not magical.

00:14:53.000 --> 00:14:58.000
So in short, trust is earned and sustained
by accepting responsibility for our

00:14:58.000 --> 00:15:02.000
actions and their outcomes.
Those with power earn and sustain

00:15:02.000 --> 00:15:03.001
trust through what they do.

00:15:04.000 --> 00:15:09.001
But those with power must extend trust
by default to others by accepting and

00:15:09.001 --> 00:15:11.001
recognizing them for who they are.

00:15:12.000 --> 00:15:16.001
Trust in a global context requires
acknowledging, valuing, and developing both

00:15:16.001 --> 00:15:20.001
kinds of trust in our communities.
But the big word, the big

00:15:20.001 --> 00:15:22.000
important scary word is equity.

00:15:22.001 --> 00:15:27.001
And it's very difficult to kind of,
we talk about equity, but it's actually very

00:15:27.001 --> 00:15:33.000
slippery. It's very elusive concept to define.
And sometimes equity is

00:15:33.000 --> 00:15:34.001
mistaken for diversity.

00:15:35.000 --> 00:15:40.000
And diversity is certainly a component,
but diversity is not what equity is all

00:15:40.000 --> 00:15:44.000
about. Diversity, in fact,
is often used as a quantitative rather

00:15:44.000 --> 00:15:45.001
than a qualitative metric.

00:15:45.001 --> 00:15:51.001
Which opens it up to gaming. It opens
it up to acts that are performative. It

00:15:51.001 --> 00:15:57.001
acts, it opens up, you know,
the about us page on a corporate website and

00:15:57.001 --> 00:16:02.000
counting the number of black and brown faces,
which really doesn't really mean

00:16:02.000 --> 00:16:05.001
anything.
And it doesn't, it's not a symbol of equity.

00:16:06.001 --> 00:16:11.001
Nor is it inclusion can be simply inclusion.
Inclusion is a sense of belonging

00:16:11.001 --> 00:16:16.000
and inclusion can be a step toward equity,
but even those who feel

00:16:16.000 --> 00:16:18.000
included may not experience it.

00:16:18.000 --> 00:16:23.001
Because inclusion alone ignores those
power structures and ignores those power

00:16:23.001 --> 00:16:28.000
imbalances.
Equity is not is also not the same as equality.

00:16:28.001 --> 00:16:33.000
Equality assumes that there's a level
playing field. Equality assumes that

00:16:33.000 --> 00:16:37.001
everyone is starting from the same place
with the same advantages, the same

00:16:37.001 --> 00:16:39.001
privileges and the same opportunities.

00:16:40.000 --> 00:16:44.000
And this ignores disparate starting points,
disparate contacts and disparate

00:16:44.000 --> 00:16:48.000
needs.
And it assumes that mere access is enough to

00:16:48.000 --> 00:16:49.001
create opportunities for equity.

00:16:49.001 --> 00:16:55.000
And I think this is fundamentally the
Achilles heel of open. So if equity is not

00:16:55.000 --> 00:16:58.001
diversity, it's not inclusion,
it's not equality, then what is it? Why is it

00:16:58.001 --> 00:17:00.001
shared definition so it will come by?

00:17:01.000 --> 00:17:05.001
There's certainly a component of fairness
or justice, but who decides what is

00:17:05.001 --> 00:17:07.000
fair? Who decides what is just?

00:17:08.000 --> 00:17:11.001
These concepts are not absolute.
They're shaped by each community or each

00:17:11.001 --> 00:17:16.000
individual's worldviews and experiences.
The definition of equity, in fact, may

00:17:16.000 --> 00:17:18.000
be a perpetually moving target.

00:17:18.001 --> 00:17:22.001
And the fact that it's difficult for us
to define equity as a society is because

00:17:22.001 --> 00:17:24.001
we've never actually had it.

00:17:26.001 --> 00:17:31.001
We have to understand that equity is both
a process and an outcome, that the most

00:17:31.001 --> 00:17:35.000
equitable way to define equity
may be to leave the definition

00:17:35.000 --> 00:17:36.001
to individual communities.

00:17:37.000 --> 00:17:42.001
And this requires not mere consultation,
but actual empowerment. Consultation

00:17:42.001 --> 00:17:47.001
reinforces very often wrong idea
that we know what's best for you.

00:17:48.000 --> 00:17:52.001
And that sustains existing power imbalances
and it sustains systemic injustice.

00:17:53.000 --> 00:17:56.001
It can be a form of digital colonialism
and it can certainly be performative.

00:17:57.000 --> 00:18:01.000
Rather, we have to understand who is
impacted by our decisions, who is impacted

00:18:01.000 --> 00:18:05.001
by our technology, who is impacted by open.
It makes sure that they are

00:18:05.001 --> 00:18:08.001
meaningfully empowered in
the decisions that are made.

00:18:09.001 --> 00:18:14.000
In short, those with power,
those with privilege must yield that power.

00:18:15.000 --> 00:18:19.000
What we're seeing over the past couple
of years as discussions of ethics and

00:18:19.000 --> 00:18:23.001
responsibility are taking the open world
by storm, what we're seeing in the

00:18:23.001 --> 00:18:27.001
pushback is that the status
quo has an immune system.

00:18:28.001 --> 00:18:33.001
Systems of oppression are dynamic and
they constantly evolve. The naive belief

00:18:33.001 --> 00:18:37.001
that open all alone will magically,
universally lead to just and equitable

00:18:37.001 --> 00:18:40.000
outcomes sustains these systems.

00:18:40.001 --> 00:18:44.001
Achieving better outcomes globally requires
to think beyond the legal definition

00:18:44.001 --> 00:18:49.000
of open. We have to look beyond vanity metrics.
We have to look beyond adoption.

00:18:49.001 --> 00:18:53.001
We have to continually assess our real
world impact. And we're starting to see

00:18:53.001 --> 00:18:56.001
recognition of that fact in the
broader digital commons ecosystem.

00:18:57.001 --> 00:19:01.000
The Internet Archive was its D-Web principles
that say the principles define the

00:19:01.000 --> 00:19:04.000
values based on enabling agency of all people.

00:19:04.001 --> 00:19:08.001
Wikimedia launched its Knowledge Equity
Fund in response to the Black Lives

00:19:08.001 --> 00:19:13.000
Matters protest of 2020 and that's designed
to address systems of racial bias and

00:19:13.000 --> 00:19:15.000
inequality around the world.

00:19:15.001 --> 00:19:18.000
The Creative Commons Five Year Strategy,
which I was honored to be able to

00:19:18.000 --> 00:19:22.001
collaborate with them on a consult with
them on, says we must expand our focus

00:19:22.001 --> 00:19:27.000
beyond copyright because content sharing
could be undermined by exploitation and

00:19:27.000 --> 00:19:32.000
violations of non copyright norms that
disproportionately impact marginalized

00:19:32.000 --> 00:19:36.000
communities. And they go on to say we
know that the open sharing ecosystem is

00:19:36.000 --> 00:19:39.000
broken and we stand ready to fix it.

00:19:39.001 --> 00:19:42.001
It's time for us to broaden our
thinking about our work, our sense of

00:19:42.001 --> 00:19:44.001
responsibility,
our mechanisms for accountability.

00:19:45.001 --> 00:19:48.001
And I don't just mean accountability
to our creator communities or to our

00:19:48.001 --> 00:19:53.000
adopters or our users, but accountability
to our broader global society.

00:19:53.001 --> 00:19:59.000
Respect, mutual trust and equity are
interconnected values. They're not side

00:19:59.000 --> 00:20:03.000
effects of open. Open is not an end to itself.

00:20:03.001 --> 00:20:08.000
The promise of open won't be fulfilled
by our intentions, but rather by our

00:20:08.000 --> 00:20:10.000
actions and their real impact.

00:20:11.000 --> 00:20:15.000
Values that we merely express but that
don't influence our behavior are not

00:20:15.000 --> 00:20:17.001
really values at all. They're lies that we tell

00:20:17.001 --> 00:20:19.000
ourselves to avoid accountability.

00:20:20.000 --> 00:20:25.001
Respect, trust and equity can't just be
words that we speak. They must be words

00:20:25.001 --> 00:20:30.001
that we listen for. Words that are spoken
not by those of us in power, those of

00:20:30.001 --> 00:20:34.000
us with influence and those of us
with privilege, but by those to

00:20:34.000 --> 00:20:35.001
whom we yield that power.

00:20:37.000 --> 00:20:37.001
Let's listen.

00:20:39.000 --> 00:20:40.000
Thank you.

00:20:48.000 --> 00:20:54.001
Thank you so much, Coraline.
When you listen for

00:20:54.001 --> 00:20:58.000
the things that you're listening for,
tell me what you

00:20:58.000 --> 00:20:59.001
hear. Tell me what you see.

00:21:01.000 --> 00:21:06.000
And hear when you witness respect,
trust and equity.

00:21:09.001 --> 00:21:16.000
Aside of relief, the joy on someone's
face of having their struggles

00:21:16.000 --> 00:21:21.001
recognized and having their concerns and
their needs prioritized and how rare and

00:21:21.001 --> 00:21:23.000
how magical that can be.

00:21:35.001 --> 00:21:39.001
And I think [...] hear as people being
thankful about the idea that things like

00:21:39.001 --> 00:21:46.000
equity and things that mutuality are
zero-sum game. So what I hear is people

00:21:46.000 --> 00:21:47.001
being thankful that they're being listened to.

00:21:47.001 --> 00:21:54.000
And I see my responsibility as really
the goal of the work that I do

00:21:54.000 --> 00:21:59.001
in my life about distributing agency.
So I was so happy to see agencies

00:21:59.001 --> 00:22:02.000
specifically called out in the DWEP principle.

00:22:02.000 --> 00:22:07.001
Because I think that's what it's all about.
It's about empowering people, often

00:22:07.001 --> 00:22:11.001
the least powerful among us,
to make decisions about the things that impact

00:22:11.001 --> 00:22:15.000
themselves, their lives, their dreams,
their communities, their world.

00:22:16.001 --> 00:22:22.000
Coraline, Moav asks,
do you have any star examples of communities

00:22:22.000 --> 00:22:23.001
that embody these goals?

00:22:25.001 --> 00:22:32.001
Whenever I'm asked about the best open
source community or the kindest or the

00:22:32.001 --> 00:22:38.000
most equitable open source community,
I always point to ifme.org.

00:22:38.001 --> 00:22:44.001
And ifme.org is an open source
project that creates a community for

00:22:44.001 --> 00:22:51.000
people, including myself, who live with
mental health challenges. And of course,

00:22:51.000 --> 00:22:56.001
on a topic like mental health,
things like privacy and safety are paramount.

00:22:57.000 --> 00:23:03.001
And I'm always so impressed by that
community and the leaders in that community

00:23:03.001 --> 00:23:10.000
about how they create that sense of
safety and respect, not only for their

00:23:10.000 --> 00:23:13.000
users, but also for the people
participating in the project.

00:23:13.001 --> 00:23:18.000
Not just from a code of conduct,
but by being transparent about how the project

00:23:18.000 --> 00:23:22.001
is governed and being very explicit about
the kinds of contributions they look

00:23:22.001 --> 00:23:26.000
for and valuing all forms
of contributions equally.

00:23:26.001 --> 00:23:31.001
I really always hold them up as a
as just a shining example of what

00:23:31.001 --> 00:23:33.000
open source can be.

00:23:34.000 --> 00:23:40.001
You mentioned in your talk that we
need to get beyond the sense of vanity

00:23:40.001 --> 00:23:45.000
metrics. And I noted that and was
wondering what type of vanity

00:23:45.000 --> 00:23:46.001
metrics are you referring to?

00:23:48.001 --> 00:23:51.001
Speaking specifically in the open source world.

00:23:53.000 --> 00:23:57.001
The measure of success of an open source
project is the number of stars you have

00:23:57.001 --> 00:24:01.000
under GitHub repo, the number of
followers you have under GitHub repo,

00:24:01.001 --> 00:24:03.000
and the number of adoptions you have.

00:24:04.000 --> 00:24:09.001
And these are all quantitative metrics,
but they don't really speak to how what

00:24:09.001 --> 00:24:12.001
you're creating is actually
being used in the world

00:24:12.001 --> 00:24:14.001
about the real world impact of it.

00:24:15.000 --> 00:24:17.000
And I've said before that.

00:24:18.001 --> 00:24:22.001
We measure the things we value, but we
also only value the things we can measure.

00:24:23.000 --> 00:24:29.000
And I think that is very much a product
of the meritocratic underpinnings of open

00:24:29.000 --> 00:24:34.000
source, the notion that social
currency is compensation enough.

00:24:35.000 --> 00:24:39.001
And I think it's really time for us to
rethink those sorts of things, rather than

00:24:39.001 --> 00:24:45.001
saying Facebook adopted my adopted my
JavaScript library. What if instead we say

00:24:45.001 --> 00:24:48.000
the fme.org project uses my JavaScript

00:24:48.000 --> 00:24:50.000
library. Those two things are not equivalent.

00:24:52.000 --> 00:24:56.001
I want to open this up to other people's
questions. So feel free to raise your

00:24:56.001 --> 00:25:01.000
hand and I will try and call on you or
you can drop your question in the chat.

00:25:01.001 --> 00:25:06.001
I see that one of the architects,
the leaders of the movement to create the

00:25:06.001 --> 00:25:11.000
principles my she calisthen is in the house.
She's coming to us, I think, from

00:25:11.000 --> 00:25:16.000
Japan, where she's now a grad student
my if you want to ask a question or

00:25:16.000 --> 00:25:18.000
unmute we welcome that.

00:25:19.001 --> 00:25:20.000
[...] going to turn it over to you.

00:25:23.000 --> 00:25:28.000
Meanwhile, I also want to ask you a little
bit about the ethical source movement

00:25:28.000 --> 00:25:32.001
and the organization for ethical source
that you're now leading. Tell us about

00:25:32.001 --> 00:25:35.000
the goals,
the mission and the work of that group.

00:25:36.000 --> 00:25:41.001
I want to I want to start by by sharing
something of a personal transformation

00:25:41.001 --> 00:25:47.000
that I went through a few years ago,
I've been I've been working for justice and

00:25:47.000 --> 00:25:50.000
equity in tech and in particular an
open source for about a decade now.

00:25:51.000 --> 00:25:55.000
And in the early days with
the tech feminist movement.

00:25:56.001 --> 00:26:02.000
Of the 20 teens, there's a cohort of us
who are all we had each other's we had

00:26:02.000 --> 00:26:07.001
each other's backs, but we all had our
own sort of passion projects that that we

00:26:07.001 --> 00:26:12.001
were pursuing whether it be publications
or you know codes of conduct or whatever

00:26:12.001 --> 00:26:15.001
our particular area of
interest and expertise was.

00:26:16.001 --> 00:26:22.001
And it was very much I think that the
movement in general failed to meet some of

00:26:22.001 --> 00:26:27.001
its goals because of that fact,
because we were all operating independently.

00:26:28.001 --> 00:26:34.000
And one of the principles I try to live
by is to find actionable feedback and

00:26:34.000 --> 00:26:40.000
even the most vitriolic criticism and one
criticism that one particular critic.

00:26:40.001 --> 00:26:46.000
Was was very insistent upon his core line
always works alone and I took that to

00:26:46.000 --> 00:26:51.001
heart and in 2019 when I saw the the
ethical crisis that open source was facing.

00:26:52.000 --> 00:26:56.000
I took that to heart and I knew this was
a problem that was a lot bigger than me

00:26:56.000 --> 00:26:59.000
and it couldn't be something
that was a passion project.

00:26:59.000 --> 00:27:04.000
So I built a movement and then I built an
organization and today the organization

00:27:04.000 --> 00:27:10.001
for ethical source, we have about 250
members across 17 i'm sorry 12 time zones.

00:27:11.001 --> 00:27:16.000
We are maybe one third to one half software
developers and engineers and the rest

00:27:16.000 --> 00:27:19.001
of our community is multi
disciplinary and global.

00:27:19.001 --> 00:27:26.000
We have ethicists we have AIDS workers,
we have legal professionals, we have

00:27:26.000 --> 00:27:31.001
social sociologists anthropologists,
I think the problems that were solving not

00:27:31.001 --> 00:27:35.000
only are bigger than one person and
not only bigger than one discipline.

00:27:36.000 --> 00:27:41.000
But bigger than one organization and
that's why i'm so pleased that the oes has

00:27:41.000 --> 00:27:46.001
been able to partner with the Internet
archive with. creative comments with these

00:27:46.001 --> 00:27:51.000
other stewards of the digital comments
because you know I recognize these

00:27:51.000 --> 00:27:54.000
problems are are very big and these
problems are very complicated.

00:27:54.001 --> 00:27:58.000
And we can't do the engineering thing that
we're trying to do all of our careers

00:27:58.000 --> 00:28:01.001
of sitting down and solving the
problems from first principles.

00:28:02.001 --> 00:28:07.001
I think we have just time for one more
question, but it's a good one from Maxine

00:28:07.001 --> 00:28:14.001
a lot of open source projects are run by
a bd fl a benevolent dictator for life,

00:28:14.001 --> 00:28:19.001
would it be beneficial for open source
projects to push for more democratic

00:28:19.001 --> 00:28:21.000
forms of governance.

00:28:23.000 --> 00:28:29.000
And one of the lessons that I learned
through my engineering career is that.

00:28:30.000 --> 00:28:35.001
Decisions should be made by the people
who are most affected by the outcomes of

00:28:35.001 --> 00:28:42.001
those decisions and and part of a
reflection of that is, I want to be.

00:28:42.001 --> 00:28:49.000
Not directive and not try to
impose the values that I have on

00:28:49.000 --> 00:28:54.001
other people, but rather to allow to to
again distribute agency, I believe that

00:28:54.001 --> 00:29:00.000
open source projects. should be representative,
but there are lots of ways that

00:29:00.000 --> 00:29:04.000
representation can happen, even with
the benevolent dictator for life model.

00:29:04.000 --> 00:29:11.000
And I see bd fl largely being employed
largely being deployed as a governance

00:29:11.000 --> 00:29:14.000
strategy for small open source
projects and that's probably fine.

00:29:15.000 --> 00:29:18.001
But if you look at a larger open source
project and i'm going to pick on i'm

00:29:18.001 --> 00:29:23.000
going to pick i'm going to pick on
chromium for here for a minute.

00:29:24.000 --> 00:29:28.001
We have an open source project that
essentially is being exploited it's

00:29:28.001 --> 00:29:35.000
exploiting free labor forward
Google's own ends and 2014 or 2015.

00:29:36.001 --> 00:29:41.000
Google decided to remove support for
users user defined style sheets from the

00:29:41.000 --> 00:29:43.000
chrome browser from the chromium browser.

00:29:43.000 --> 00:29:49.000
And there was a huge outcry from the
contributor base because user defined style

00:29:49.000 --> 00:29:53.001
sheets are a tool that's often used by
people with with different disabilities

00:29:53.001 --> 00:29:55.000
as an accessibility tool.

00:29:56.001 --> 00:30:02.001
And the outcry from the Community was met
with with a haughtiness and a dismissal

00:30:02.001 --> 00:30:09.001
by the Google core team. who literally
said we we were not going to give you what

00:30:09.001 --> 00:30:13.000
you want, it doesn't make matter how much
noise you make this is not a democracy.

00:30:15.000 --> 00:30:19.001
And I think I think if you know if we
look at the scale of a project like

00:30:19.001 --> 00:30:24.000
chromium. that's where representative and
transparent governance really needs to

00:30:24.000 --> 00:30:29.001
happen if you have a javascript
library with 12 with 12 contributors

00:30:29.001 --> 00:30:31.000
it's not as important.

00:30:32.000 --> 00:30:36.000
We have to understand the context we
have to understand scale and make the

00:30:36.000 --> 00:30:39.001
decisions that are right for our
communities within those contexts.

00:30:40.001 --> 00:30:45.000
Well, Coraline thank you so much for your
work for your leadership, we hope that

00:30:45.000 --> 00:30:49.000
you'll stick around and join us in
gather town so people can ask you more

00:30:49.000 --> 00:30:51.000
questions directly and please.

00:30:52.001 --> 00:30:58.001
Join learn more about Coraline's
organization and I hope you'll

00:30:58.001 --> 00:31:00.000
drop it in chat so people can learn.

00:31:00.000 --> 00:31:02.001
Oh, certainly thank you so much Wendy.

00:31:03.000 --> 00:31:03.001
Thank you.

00:31:05.000 --> 00:31:11.001
Well, everyone on that note,
we want to now turn and take you around

00:31:11.001 --> 00:31:17.000
the world we're going to be having seven
lightning talks some from Warsaw from

00:31:17.000 --> 00:31:20.000
Lisbon from the metaverse.

00:31:20.001 --> 00:31:25.001
And here's here's the rules,
you each have five minutes to present

00:31:25.001 --> 00:31:27.000
and when you hear.

00:31:27.001 --> 00:31:33.000
A quack that means you have one minute
left and then two minutes left two quacks

00:31:33.000 --> 00:31:37.001
means you're completely out of time,
even for questions so let's get started.

00:31:38.001 --> 00:31:44.000
First, a woman who in this part of the
world needs no introduction Jenny Ryan

00:31:44.000 --> 00:31:48.000
she's coming to you from Oakland
she's the co founder of so

00:31:48.000 --> 00:31:49.001
many terrific nonprofits.

00:31:50.000 --> 00:31:56.000
Omni commons pseudo mesh pseudo room,
but today she's joining us as the project

00:31:56.000 --> 00:32:03.000
manager of the CINO browser CINO
meaning censorship know. it's a project

00:32:03.000 --> 00:32:09.001
of one of my favorite organizations
equality and some of the best. makers

00:32:09.001 --> 00:32:15.000
of tools that protect human rights in
the world work for equality, so please

00:32:15.000 --> 00:32:19.001
please welcome Jenny Ryan
talking about her project CINO.

00:32:23.000 --> 00:32:28.001
Well, just to start, I think,
thank you so much Wendy for that very generous

00:32:28.001 --> 00:32:35.001
introduction and it's it's nice to reconnect
with a D web community here and now.

00:32:37.001 --> 00:32:43.000
Just quickly going to make
sure I am sharing my screen

00:32:43.000 --> 00:32:45.000
properly so one moment.

00:32:58.001 --> 00:33:00.000
There you go.

00:33:01.001 --> 00:33:08.001
Okay, seeing the first slide.
yeah as the intro so yeah many of you might

00:33:08.001 --> 00:33:13.000
have met me in the context of pseudo mesh
previously in people's open network.

00:33:13.001 --> 00:33:20.001
All sort of ongoing in kind of pandemic

00:33:20.001 --> 00:33:22.001
hiatus at the moment.

00:33:24.000 --> 00:33:28.000
But recently I started working for a
really wonderful organization called

00:33:28.000 --> 00:33:34.000
equality building decentralized
tools for enabling

00:33:34.000 --> 00:33:37.001
free speech and access to information.

00:33:39.001 --> 00:33:45.001
In in multiple concrete projects,
one of them that i'm working on is called

00:33:45.001 --> 00:33:48.000
censorship now are CINO browser.

00:33:49.001 --> 00:33:56.001
And I will dig into that further shortly, but I

00:33:56.001 --> 00:34:01.000
did have kind of a a
premise and in all of this.

00:34:03.000 --> 00:34:07.001
And forgive me for navigating back.

00:34:09.001 --> 00:34:16.000
That riffs very much off of everything.
carlin's just been saying.

00:34:18.000 --> 00:34:21.001
And hard to digest you know trying to.

00:34:23.000 --> 00:34:29.001
Make this also a conversation
about the point of

00:34:29.001 --> 00:34:34.000
decentralization and and the
promises and possibilities.

00:34:36.000 --> 00:34:42.001
And who we've taken to account as we
build these tools whose voices are heard

00:34:42.001 --> 00:34:44.000
how we account for.

00:34:45.001 --> 00:34:52.000
Yes, security privacy and and
making sure everything is

00:34:52.000 --> 00:34:53.001
very transparent.

00:34:55.000 --> 00:35:02.000
Throughout the process of building
and outreach around. onboarding

00:35:02.000 --> 00:35:05.000
people to use them in the first so.

00:35:06.001 --> 00:35:10.000
Just to start we all care
about decentralization.

00:35:11.000 --> 00:35:15.001
And returning to the core ideals of the
Internet as a distributed uncontrollable

00:35:15.001 --> 00:35:18.000
wellspring of thoughts ideas and information.

00:35:19.001 --> 00:35:24.000
For those with privilege and technical
abilities I contend that the crux of your

00:35:24.000 --> 00:35:27.000
energy should be spent on ensuring
this fountain of knowledge

00:35:27.000 --> 00:35:28.001
is accessible to everybody.

00:35:30.000 --> 00:35:35.001
In particularly those oppressed by actors
and institutions seeking to control and

00:35:35.001 --> 00:35:39.000
regulate communication flows so really.

00:35:39.000 --> 00:35:45.000
I ideally we're building these tools

00:35:45.000 --> 00:35:48.001
informed by the people that are going
to use them and the risks that they're

00:35:48.001 --> 00:35:54.001
really facing and most of us are not
intimately familiar with those risks.

00:35:56.001 --> 00:36:00.001
Probably wouldn't be in this conversation
right now if we if we really were.

00:36:02.000 --> 00:36:04.000
So there's that.

00:36:05.000 --> 00:36:11.001
And we really need real dedicated
contributors developers I

00:36:11.001 --> 00:36:18.000
just perspectives.
informing the design of these technologies to

00:36:18.000 --> 00:36:22.001
ensure actual digital human rights.

00:36:24.000 --> 00:36:28.001
So i'm going to talk about one such
project senior browser I only have a few

00:36:28.001 --> 00:36:31.000
minutes. and.

00:36:32.001 --> 00:36:37.001
Specifically, it is a mobile web

00:36:37.001 --> 00:36:40.001
browser. that's designed.

00:36:41.001 --> 00:36:48.001
On a peer to peer functionality
basis to store and share cached

00:36:48.001 --> 00:36:52.000
web content that may otherwise
be blocked by by sensors.

00:36:53.001 --> 00:36:59.000
So it's using decentralization as a means
to deliver and share web content and as

00:36:59.000 --> 00:37:04.000
a countermeasure to web censorship writ large.

00:37:09.001 --> 00:37:13.000
apologies going back and forth here.

00:37:14.000 --> 00:37:14.001
So.

00:37:15.000 --> 00:37:18.001
The general one on how it works.

00:37:19.000 --> 00:37:25.000
Most web traffic in countries that filter
the Internet goes through centralized

00:37:25.000 --> 00:37:31.001
exchanges we're all familiar with these
Google Facebook Twitter Amazon so on.

00:37:32.001 --> 00:37:39.001
And that makes it very easy for
sensors to block requests for that

00:37:39.001 --> 00:37:44.001
content based on domains and and again these

00:37:44.001 --> 00:37:46.001
centralized. servers.

00:37:49.000 --> 00:37:53.001
In the case of an active censorship scenario.

00:37:55.000 --> 00:38:02.000
This could be.
very commonly experienced in China in Iran.

00:38:03.000 --> 00:38:09.000
and actually an increasing amount
of countries across the planet.

00:38:10.000 --> 00:38:17.000
And and that makes it essentially impossible
to just get that content using in

00:38:17.000 --> 00:38:23.000
country. general mobile data that most
people are going to be using to try

00:38:23.000 --> 00:38:24.001
to access a website right.

00:38:24.001 --> 00:38:31.000
So CINO is built off of.

00:38:33.000 --> 00:38:36.001
Firefox for Android.

00:38:39.001 --> 00:38:46.001
Is a tool an application that stores shares

00:38:46.001 --> 00:38:51.000
caches web content and
shares it peer to peer over.

00:38:51.001 --> 00:38:58.001
Using functionally bit torrents
distributed hash table. and other

00:38:58.001 --> 00:39:02.001
ideas in the works for more
local sharing opportunities.

00:39:06.000 --> 00:39:12.000
Once the website is accessed by someone
using CINO browser that content is

00:39:12.000 --> 00:39:17.000
stored. shared and made available in this.

00:39:17.001 --> 00:39:19.001
Distribute cache of content.

00:39:22.001 --> 00:39:28.000
And just a little overview of what's under
the hood again I think I've mentioned

00:39:28.000 --> 00:39:32.001
all of this that it's built
off of Firefox for Android.

00:39:33.000 --> 00:39:40.000
In iteration of it utilizes bit
torrents to HT for pure sharing of

00:39:40.000 --> 00:39:45.001
content and the we net library,
which is an open source library.

00:39:46.000 --> 00:39:49.000
That we are just really starting to get into.

00:39:50.001 --> 00:39:57.000
Making more available for third
party applications to use to enable

00:39:57.000 --> 00:39:58.001
distributed.

00:40:00.000 --> 00:40:06.000
And peer to peer sharing of web content
through their applications so some links

00:40:06.000 --> 00:40:10.001
here and happy to share after
and looking forward to the

00:40:10.001 --> 00:40:12.001
gather town conversation.

00:40:16.000 --> 00:40:17.001
Yeah, there's.

00:40:19.000 --> 00:40:21.001
The final slide i'll just keep that up.

00:40:23.000 --> 00:40:24.000
Thanks for the quacks.

00:40:25.000 --> 00:40:28.001
Thanks Jenny [...] at more over in gather town.

00:40:30.000 --> 00:40:36.000
Right we're going to go from Oakland to Warsaw,
where it is like 1am plus in the

00:40:36.000 --> 00:40:40.001
morning next up is a l ron he's
the co founder of asteroids.

00:40:41.000 --> 00:40:46.000
He has a PhD in mathematics from free
university in Berlin, I know that he helped

00:40:46.000 --> 00:40:49.000
to write some of the specs
for Germans blockchain.

00:40:50.000 --> 00:40:56.000
And also he's the founder of many startups,
the latest of which is asteroids,

00:40:56.000 --> 00:41:01.001
which is a search engine for decentralized
websites welcome to the D web meetup.

00:41:02.000 --> 00:41:06.000
Hi, thank you very much for the introduction
i'm actually so happy to be here,

00:41:06.000 --> 00:41:10.000
but I came in the middle of the night,
but you know that's why I have coffee for.

00:41:12.001 --> 00:41:18.001
yeah so i'm a and i'm doing a project
which is called the asteroids asteroids

00:41:18.001 --> 00:41:20.001
actually has a kind of three parts.

00:41:21.000 --> 00:41:25.000
One of them is the future is the vision,
what we want to build one of it is the

00:41:25.000 --> 00:41:27.001
past what we already did and one of them is the

00:41:27.001 --> 00:41:29.000
present, which is what we build now.

00:41:30.000 --> 00:41:33.000
And i'll start with our future because that's

00:41:33.000 --> 00:41:34.001
the most exciting thing why we do it.

00:41:36.000 --> 00:41:40.000
I have to say i'm quite humbled to be
here the two talks before me was super

00:41:40.000 --> 00:41:44.001
impressive and talks you're so interested
in almost wants to listen to them more

00:41:44.001 --> 00:41:49.000
than actually to give mind.
awesome event so asteroid

00:41:49.000 --> 00:41:50.001
is building a democratic web.

00:41:51.001 --> 00:41:56.000
That's that's the goal, we want to have
an alternative to the current web,

00:41:56.000 --> 00:41:57.001
which is like a democracy.

00:41:58.001 --> 00:42:03.000
This means both the web protocol and we
also have to have democratic platforms,

00:42:03.001 --> 00:42:09.000
you know imagine social media, which is
actually. governed by its own users and

00:42:09.000 --> 00:42:13.001
disconnects to what Corin said in her
first lecture or in the Q amp a that

00:42:13.001 --> 00:42:17.000
decisions should be made by the people
who are most affected by these decisions.

00:42:17.001 --> 00:42:22.001
And obviously it's the users of the web
who are affected by this decision and

00:42:22.001 --> 00:42:29.000
they should go from the web. it's an
entity to the court web people are members

00:42:29.000 --> 00:42:36.000
of the democratic web, we are not users
and together they govern that like you do

00:42:36.000 --> 00:42:40.001
in a democratic state, so there are elections
and representatives and government.

00:42:41.000 --> 00:42:46.000
I mean the whole idea is to take the
model of democratic state of democratic

00:42:46.000 --> 00:42:51.000
organizations and move it forward to
the Internet age with modernization,

00:42:51.001 --> 00:42:56.001
obviously, and with changes that
you have to do for a medium

00:42:56.001 --> 00:42:58.001
but still keep you know the call.

00:43:00.000 --> 00:43:06.001
Technically, we base it on the decentralized
web and more technically we use the

00:43:06.001 --> 00:43:11.000
ns and ipfs websites,
the main thing here is the decentralization

00:43:11.000 --> 00:43:12.001
for us is a mean to our goal.

00:43:13.001 --> 00:43:19.001
It's a mean to an end it's a tool that we
use it's not the goal and we basically

00:43:19.001 --> 00:43:23.001
use the decentralized way because
that's the only way that we know how

00:43:23.001 --> 00:43:25.000
to implement the democratic web.

00:43:26.000 --> 00:43:32.001
And the first thing that I want you to
take from this lightning talk is that if

00:43:32.001 --> 00:43:35.000
this idea of democratic web
is interesting for you.

00:43:36.001 --> 00:43:40.000
Come and talk to us, we have email and we have.

00:43:40.000 --> 00:43:42.000
[...]

00:43:44.001 --> 00:43:48.000
We are happy for for public chairs,
we are having for call because we just

00:43:48.000 --> 00:43:50.001
started the project like half a year ago,
we are we are

00:43:50.001 --> 00:43:52.000
in the first few steps and.

00:43:52.001 --> 00:43:57.000
We want input we want people to be involved,
we don't want to be doing it all

00:43:57.000 --> 00:44:01.001
ourselves, so please come and contact
us if the idea of building democratic

00:44:01.001 --> 00:44:03.001
web interest you.

00:44:04.001 --> 00:44:09.001
Now, this is the future, we are now in
the present and we cannot build this

00:44:09.001 --> 00:44:13.000
democratic web like either way,
there are many steps to take in between.

00:44:13.001 --> 00:44:19.001
So the question is, what did we do so
far and we started in April this year.

00:44:19.001 --> 00:44:26.000
And we decided to base what we do on
ENS and IPFS websites so ENS and IPFS

00:44:26.000 --> 00:44:29.001
technology we call those websites D websites.

00:44:30.001 --> 00:44:36.001
There are many other ways, I mean many
other decentralized websites, but right

00:44:36.001 --> 00:44:40.001
now for this talk in SNIPFS websites will
be what I mean when I say D websites.

00:44:42.000 --> 00:44:45.001
We identified when we started we identified
that the few challenges in this D

00:44:45.001 --> 00:44:48.000
website atmosphere and one of
the big one was discoverability.

00:44:48.000 --> 00:44:54.000
There were already a few thousand websites
and like new ones popping up every

00:44:54.000 --> 00:44:58.000
day, but it was difficult to discover
them and you couldn't keep track

00:44:58.000 --> 00:44:59.001
what is new you couldn't see the tracks.

00:45:00.001 --> 00:45:05.000
So the first thing that we built and let's
see if yes, I can do my share screen

00:45:05.000 --> 00:45:10.001
smoothly that's amazing yeah we built a
search engine for the decentralized web.

00:45:10.001 --> 00:45:14.001
This search engine is actually
the centralized website itself.

00:45:17.000 --> 00:45:18.001
Which I think is quite cool.

00:45:20.000 --> 00:45:24.001
It works quite you know normally search
engine UX is one of the things which

00:45:24.001 --> 00:45:27.000
which I think reach maturity and
you can't improve on it much or

00:45:27.000 --> 00:45:29.000
at least I don't know how to.

00:45:30.000 --> 00:45:34.001
And if you search for NFT,
which is very trendy right now, you see lots of

00:45:34.001 --> 00:45:37.000
centralized websites which do NFT.

00:45:38.001 --> 00:45:41.001
Because there are like only a few thousand
websites, we are not sure if people

00:45:41.001 --> 00:45:45.001
want to search or they just want to
see what happens, so we also have

00:45:45.001 --> 00:45:47.000
like tools for browsing websites.

00:45:48.001 --> 00:45:51.000
You can see which one are
you which one are popular.

00:45:52.000 --> 00:45:55.001
The other thing that we did is that there
is no awareness for the decentralized

00:45:55.001 --> 00:45:59.001
website ecosphere, so we started at the
center as website of the week award.

00:46:00.001 --> 00:46:03.001
And if you are interesting to see what is
what are the best ways that every week

00:46:03.001 --> 00:46:05.001
follow our Twitter and see the world.

00:46:06.000 --> 00:46:11.000
When the last thing that we do is the
present that's what we do now and what we

00:46:11.000 --> 00:46:17.000
do now is taking asteroids and turning
it into a democratic platform.

00:46:19.001 --> 00:46:23.000
Obviously, I don't have any time
to give details on it, but.

00:46:25.001 --> 00:46:29.001
If this interest you come to our medium,
we have a few articles, but we wrote

00:46:29.001 --> 00:46:34.000
about it on how we do that
I posted links in the chat.

00:46:35.000 --> 00:46:41.000
And if it really interest you, please come
and talk to us because we want to have

00:46:41.000 --> 00:46:45.000
people involved it's supposed to be a
Community website our community our discord

00:46:45.000 --> 00:46:47.001
already have 100 people, more or less,
and they are quite active, but

00:46:47.001 --> 00:46:49.001
we want more than we have want ideas.

00:46:50.000 --> 00:46:54.000
And we want to start with you know we
don't want to put on stuff that we have no

00:46:54.000 --> 00:46:58.000
idea on like how to manage a Community etc.

00:47:00.000 --> 00:47:05.000
And if you don't want to be part of it,
thank you anyway for coming and

00:47:05.000 --> 00:47:07.000
listening to me, it was a pleasure being here.

00:47:08.001 --> 00:47:10.001
I think we all want to learn more.

00:47:11.001 --> 00:47:18.000
I have seen I think people are questioning
how I introduced you I meant to say

00:47:18.000 --> 00:47:23.001
that you were a writer for for some of
Germany's blockchain specs, can you just

00:47:23.001 --> 00:47:25.001
shed a little bit of light of what you did.

00:47:26.001 --> 00:47:32.001
Sure, sure, sure I finished my PhD in
2016 and afterwards I had a start up with

00:47:32.001 --> 00:47:37.000
consulting or kind of small projects and
one of those we were hired to write.

00:47:38.000 --> 00:47:43.001
Something which is called Dean specs Dean
is the German industry organization, it

00:47:43.001 --> 00:47:49.000
was two specs about blockchain i'm not
sure what is the legal status of those

00:47:49.000 --> 00:47:53.001
specs in Germany, one of them was about
boxing terminology in the other was about

00:47:53.001 --> 00:47:55.001
blockchain notary.

00:47:55.001 --> 00:48:01.001
Like timestamping with blockchain I think
it was 2018 and I think with like oh

00:48:01.001 --> 00:48:05.001
yeah right there's a link here and I think
that it's already like expired because

00:48:05.001 --> 00:48:12.001
I think the validity of those specs
is for three years but. i'm not sure

00:48:12.001 --> 00:48:15.000
yeah that's it.

00:48:16.000 --> 00:48:21.000
Thank you, thank you, I'll will you come
back for December and have a booth so

00:48:21.000 --> 00:48:24.001
people can learn more about how
to create a democratic web.

00:48:26.000 --> 00:48:31.001
Thank you, thank you, thank you all right
i'm going to turn to another person in

00:48:31.001 --> 00:48:33.000
Europe, where it's even later.

00:48:34.001 --> 00:48:41.000
Savannah Lee is the brand manager of the
Mysterium network and she is right now,

00:48:41.000 --> 00:48:44.000
I believe in Lisbon attending the web summit.

00:48:45.000 --> 00:48:51.000
She must be super super tired, but thank
you so much for joining us to talk about

00:48:51.000 --> 00:48:55.001
Mysterium, I mean I was I was struck by
something in your introduction that.

00:48:56.000 --> 00:49:01.000
You say that only a quarter of the people
in the world have access to free and

00:49:01.000 --> 00:49:06.000
open Internet and that that's where
Mysterium comes in. it's an open source

00:49:06.000 --> 00:49:11.000
project creating a censorship resistant
layer on the Internet kind of like tour

00:49:11.000 --> 00:49:14.000
but with incentives will you tell us more.

00:49:14.001 --> 00:49:19.001
Right yeah so thanks so much for that
introduction and i'm really happy to be

00:49:19.001 --> 00:49:23.001
here, it is when I am but I love to
connect with so many people in this

00:49:23.001 --> 00:49:25.000
community new faces old ones.

00:49:25.001 --> 00:49:31.001
So thank you so just to correct that
statistic it's one quarter of the Internet's

00:49:31.001 --> 00:49:38.000
users. don't actually have full access to
it so similarly to Jenny who's working

00:49:38.000 --> 00:49:42.001
on an anti censorship or censorship
resistant kind of tool, we also are doing

00:49:42.001 --> 00:49:48.000
something very similar,
so let me just share my screen, so I can.

00:49:49.001 --> 00:49:52.000
give you more of an idea about it.

00:49:56.000 --> 00:49:57.000
Can you see.

00:49:58.001 --> 00:50:04.000
All right perfect so like Wendy said
Mysterium is an open source project we're

00:50:04.000 --> 00:50:09.001
creating a censorship resistant layer
mostly tools and web infrastructure, so we

00:50:09.001 --> 00:50:15.001
will found it in 2017 by a small team.
of developers and entrepreneurs, but now

00:50:15.001 --> 00:50:21.000
we're about 50 people spread all over the
world, so our first tool was actually a

00:50:21.000 --> 00:50:24.001
decentralized VPN which is
powered by a peer to peer

00:50:24.001 --> 00:50:26.001
marketplace on the Ethereum network.

00:50:32.000 --> 00:50:37.000
So this is a screenshot of our grafana
it's a beautiful thing to see in live

00:50:37.000 --> 00:50:40.000
action the peer to peer nature of our tool.

00:50:41.000 --> 00:50:44.000
So providers run our node
software and devices like

00:50:44.000 --> 00:50:45.001
their computers or raspberry pies.

00:50:47.000 --> 00:50:51.000
And they use the nodes to share their
Internet resources with each other, so in

00:50:51.000 --> 00:50:54.000
our case that's for residential
ips and the node network function

00:50:54.000 --> 00:50:56.000
similarly to tour network.

00:50:56.000 --> 00:51:00.000
But with the micro economy
built in and nodes are paid for

00:51:00.000 --> 00:51:01.001
the amount of traffic that they serve.

00:51:02.001 --> 00:51:06.000
So the marketplace is completely
permissionless anyone in
the world can join lend

00:51:06.000 --> 00:51:11.000
their digital freedom to the global
community and. we've kind of grown this

00:51:11.000 --> 00:51:14.001
community completely grassroots
it's been all organic,

00:51:14.001 --> 00:51:16.000
which is really humbling to see.

00:51:17.000 --> 00:51:21.000
We have about 4000 nodes now spread
around the world and a lot of the more

00:51:21.000 --> 00:51:25.001
popular regions is where they're concentrated
so the US UK where there's a little

00:51:25.001 --> 00:51:28.001
more let's say like Internet
access availability.

00:51:29.001 --> 00:51:33.001
As compared to sensitive regions,
so we have 100,000 monthly active users right

00:51:33.001 --> 00:51:37.001
now connecting to these nodes and
about 700 terabytes of monthly

00:51:37.001 --> 00:51:39.001
traffic flowing throughout the network and.

00:51:40.000 --> 00:51:44.000
We can't do any kind of logging because
of the distributed nature of the network

00:51:44.000 --> 00:51:48.000
so compared to traditional bpm
we do have quite a good value

00:51:48.000 --> 00:51:51.000
proposition, even when you're just looking.

00:51:51.001 --> 00:51:54.001
Excuse me,
looking at use cases like streaming content.

00:51:57.000 --> 00:52:03.000
So this is the interface super simple up
to use and you just select a location

00:52:03.000 --> 00:52:04.001
based on where you'd like to be.

00:52:05.000 --> 00:52:09.000
And you can pay with cryptocurrency
currently so you can remain anonymous or you

00:52:09.000 --> 00:52:14.000
can. pay with cash in the next week or
two will be integrating fiat options.

00:52:14.001 --> 00:52:18.001
And on the right is the node runners
dashboard so anyone can sign up to the

00:52:18.001 --> 00:52:22.000
network and you have this hub to kind
of track your earnings your traffic

00:52:22.000 --> 00:52:24.000
uptime and number of connections to your note.

00:52:25.001 --> 00:52:31.000
So why do we do this, just like most
people here in the D web Community

00:52:31.000 --> 00:52:32.001
primary goal is.

00:52:33.001 --> 00:52:37.000
Digital rights and Internet freedom so
freedom of information freedom of speech

00:52:37.000 --> 00:52:41.001
of the press we work really closely with
communities to help them bypass online

00:52:41.001 --> 00:52:43.001
censorship and Internet blackouts.

00:52:44.001 --> 00:52:48.001
For example, in Nigeria, about one year
ago when the Nsas protests were happening

00:52:48.001 --> 00:52:52.000
we worked with members of the
Community there during that time.

00:52:52.001 --> 00:52:56.000
To understand how we could help them
stay safe and connected and when the

00:52:56.000 --> 00:53:00.000
government for and to ban social media
platforms like Twitter we were kind of

00:53:00.000 --> 00:53:04.001
working with some ambassadors on the
ground to spread awareness and toolkits.

00:53:11.000 --> 00:53:15.001
So where we are right now is we'll be
finally launching on mainnet in a few weeks

00:53:15.001 --> 00:53:19.001
which we've been through many iterations
and test nets and now we're finally

00:53:19.001 --> 00:53:21.000
going to be releasing the full version.

00:53:21.000 --> 00:53:25.001
And we'll be growing our
ecosystem we really want to work

00:53:25.001 --> 00:53:27.000
with builders like I'll said.

00:53:28.000 --> 00:53:32.000
There's so many amazing different projects
in this space or working together, and

00:53:32.000 --> 00:53:36.000
so we kind of want to make our network
portable so you can plug into it leverage

00:53:36.000 --> 00:53:39.000
the residential IP network as you need it.

00:53:39.000 --> 00:53:44.000
We already work with proxy services data
scraping solutions even browsers and

00:53:44.000 --> 00:53:48.001
other VPN so any service that needs to
make itself globally accessible and kind

00:53:48.001 --> 00:53:51.000
of wants to help expand this
layer and make it stronger.

00:53:52.000 --> 00:53:55.001
So we're always looking to collaborate,
whether you're web to web three but yeah

00:53:55.001 --> 00:53:57.001
please do get in touch with me.

00:53:58.001 --> 00:54:04.001
So, so then I think we have time for one
question and that's what's the benefit

00:54:04.001 --> 00:54:09.000
of using Mysterium over tour,
which is already trusted it's free it doesn't

00:54:09.000 --> 00:54:12.001
encourage people to use
hardware with non free blobs.

00:54:14.001 --> 00:54:20.000
I think usability is one of them so for
a lot of people to network can be quite

00:54:20.000 --> 00:54:22.001
intimidating and it's not
probably as user friendly.

00:54:22.001 --> 00:54:27.001
For a lot of people just getting to know
censorship resistant tools, so we try to

00:54:27.001 --> 00:54:32.001
make it as we tried to lower the barriers
entry as much as we can for users.

00:54:33.001 --> 00:54:38.001
Also, it has more VPN functionality so
we're integrated with open VPN and why

00:54:38.001 --> 00:54:42.001
God, so we encrypt all the traffic so we
kind of enhanced privacy and anonymity.

00:54:43.000 --> 00:54:47.001
And then, on the node side, obviously
the incentives are all there so you're

00:54:47.001 --> 00:54:52.000
getting paid, rather than just voluntarily
running a node we kind of try and

00:54:52.000 --> 00:54:53.001
create a supply and demand model.

00:54:54.001 --> 00:54:59.000
Savannah thanks so much, and I hope
you'll also come back in December and

00:54:59.000 --> 00:55:04.000
mannequins so that people who want to
get involved can can join you. yeah we'd

00:55:04.000 --> 00:55:05.001
love that Thank you thanks [...]

00:55:06.000 --> 00:55:10.001
Thanks thanks so much okay now
we're going to turn toward Asia

00:55:10.001 --> 00:55:12.001
and we're going to hear
from some of the people.

00:55:12.001 --> 00:55:19.001
Suji Yan, he is the co founder of mask
that I owe now you know his other

00:55:19.001 --> 00:55:25.001
co founder quite well you see Lou who
leads our Shanghai node. mask asked the

00:55:25.001 --> 00:55:30.000
simple question Okay,
the D web exists, but if everyone

00:55:30.000 --> 00:55:31.001
is on Facebook and Twitter.

00:55:31.001 --> 00:55:37.000
How can you help create privacy on those
dominant platforms where people already

00:55:37.000 --> 00:55:41.000
live here to share an answer
to that and his vision of mask

00:55:41.000 --> 00:55:43.000
that I owe is Suji Yan.

00:55:45.000 --> 00:55:48.000
Hello everyone Suji here.

00:55:49.000 --> 00:55:54.000
I was born in Shanghai and right now
in New York City for the NFT but

00:55:54.000 --> 00:55:55.001
calling from the mid-arvers.

00:55:56.001 --> 00:56:03.000
I'd love to share our story of the mass
network and especially how to potentially

00:56:03.000 --> 00:56:09.000
have the mass adoption for the decentralized
web or the next generation of web on

00:56:09.000 --> 00:56:13.001
the mainstream platform we use every day,
namely Facebook and Twitter.

00:56:15.001 --> 00:56:16.000
Hello.

00:56:19.001 --> 00:56:20.000
So.

00:56:21.000 --> 00:56:27.001
From the very beginning of my career,
I was a journalist and also a engineer

00:56:27.001 --> 00:56:32.001
I study and wrote a lot of the
early history of the web 1.0.

00:56:33.000 --> 00:56:38.000
Which that time everyone saying there was
evil monopoly company called Microsoft

00:56:38.000 --> 00:56:43.001
Windows and we also know that time
night is the Internet exists.

00:56:43.001 --> 00:56:50.001
How can everyone without leaving Windows
use the Internet very easy solution

00:56:50.001 --> 00:56:55.000
browser in store and software
on the monopolized operating

00:56:55.000 --> 00:56:57.000
system Windows and double click.

00:56:57.000 --> 00:57:03.001
When I go to the open web at least much
more open web compared to think so I

00:57:03.001 --> 00:57:10.000
learned this story and during my traveling
my working with many activists and

00:57:10.000 --> 00:57:15.000
engineers, I figure out probably will be
the same thing for our our revolution.

00:57:15.000 --> 00:57:20.000
Today, pretty much we are facing the
same problem that most of the existing

00:57:20.000 --> 00:57:26.001
users, your grandma's my friends are
stuck in the mainstream platform meta

00:57:26.001 --> 00:57:28.001
Facebook or Twitter.

00:57:30.001 --> 00:57:34.000
And also we heard there's something called
decentralized web in a Western point.

00:57:34.000 --> 00:57:40.000
I know we see decentralized storage domain,
you know, sensitive system power, but

00:57:40.000 --> 00:57:45.000
there's no way to use them.
It's really hard to to use or doubt.

00:57:45.001 --> 00:57:50.001
How can we just, how about let's just put
this thing together and in in general

00:57:50.001 --> 00:57:54.000
on top of the face when Twitter.
So that's the idea of mass time.

00:57:54.000 --> 00:58:00.000
I own mass network. So this many functionality
we achieve in the past few year we

00:58:00.000 --> 00:58:03.000
started in early 2018 speak for a year.

00:58:03.001 --> 00:58:10.001
I will do some real use case to show you
what is capable to do in mass network.

00:58:11.000 --> 00:58:13.001
And we're going to also
provide several case study.

00:58:13.001 --> 00:58:20.000
So this is my browser. We see chromium browser,

00:58:21.000 --> 00:58:25.001
you know, open source browser core is
pretty much the same thing as other

00:58:25.001 --> 00:58:30.001
mainstream browser installed the mass
extension on my brother and I can do this.

00:58:30.001 --> 00:58:35.000
I internet archive and

00:58:35.000 --> 00:58:37.001
D web.

00:58:40.000 --> 00:58:43.000
Let's decentralized the web.

00:58:44.000 --> 00:58:49.001
I'll do this for demo purpose so it's all
encrypted for everyone. It will turns

00:58:49.001 --> 00:58:56.001
into gibberish now so I can turn into
stenography. So, I will, I will able to

00:58:56.001 --> 00:58:58.001
able to decrypt it automatically on my Twitter.

00:58:58.001 --> 00:59:00.001
[...]

00:59:02.000 --> 00:59:06.000
So, anyone who installed
the mask can can see that I

00:59:06.000 --> 00:59:08.000
can also change the recipient.

00:59:09.000 --> 00:59:11.001
It's pretty much like the PGP
I can add different recipient.

00:59:13.000 --> 00:59:18.001
For example, I want to have a topic between
any serum guy, and maybe other people

00:59:18.001 --> 00:59:22.000
I can add them in the in the in
the chat in the conversation.

00:59:22.001 --> 00:59:24.000
So this is for something I we achieved.

00:59:24.000 --> 00:59:30.001
We caught here encryption encryption.
And then if you can send over message you

00:59:30.001 --> 00:59:35.001
can also able to send over file,
which is also some kind of message in

00:59:35.001 --> 00:59:38.000
IPFS or in file coin.

00:59:38.001 --> 00:59:41.000
For example, let me take a screenshot here.

00:59:42.000 --> 00:59:49.000
This is more screenshot and we [...
] for we can do this in a file service. You

00:59:49.000 --> 00:59:53.001
can use decentralized CDN you can make
it to see encrypted and just upload this

00:59:53.001 --> 00:59:59.000
thing by fun decentralized no somewhere
near you, and you upload this

00:59:59.000 --> 01:00:01.000
into the decentralized storage.

01:00:02.000 --> 01:00:08.000
Hi again, and I can use image payload,
so it will be ultimately encrypted and

01:00:08.000 --> 01:00:10.001
and this file going to show up here.

01:00:11.001 --> 01:00:12.001
Click the file going to see the file.

01:00:13.001 --> 01:00:19.001
Yeah, and not only this, we can also send
money. So this is a game me during the

01:00:19.001 --> 01:00:24.001
Lunar New Year, I send money and metallic
also send money over on top of Twitter,

01:00:24.001 --> 01:00:26.001
so we can send money on Twitter, fun.

01:00:26.001 --> 01:00:32.000
What else can you do, like NFT right
everyone like NFT you know it's a digital

01:00:32.000 --> 01:00:36.000
art. What if about you can put
NFT right on top of Twitter.

01:00:37.000 --> 01:00:41.000
It's obvious David had got too many NFT I
think it's even. Oh, okay, it's loading

01:00:41.000 --> 01:00:45.001
here. So, people sending him NFT
and we put that on top of Twitter.

01:00:45.001 --> 01:00:51.001
What if you can donation yeah so you
can even donate on Twitter on whatever

01:00:51.001 --> 01:00:57.000
platform you want. So, eventually,
the goal of mass network is try to say, hey,

01:00:57.000 --> 01:01:01.000
people don't leave Twitter Facebook
because it's impossible to, you

01:01:01.000 --> 01:01:02.001
know, move to another platform.

01:01:02.001 --> 01:01:09.001
How about let's stay here. And we build
a lot of things on top. So, math network

01:01:09.001 --> 01:01:14.000
is a crypto and decentralized web
project but also development SDK,

01:01:14.001 --> 01:01:16.000
people can build something on top.

01:01:16.001 --> 01:01:21.000
If you have skill it was decentralized storage,
then you can say, Oh, today

01:01:21.000 --> 01:01:24.001
Twitter Facebook don't support it but I
will support it for them. If you have

01:01:24.001 --> 01:01:28.000
skill for NFT and art,
you can say oh I want to integrate

01:01:28.000 --> 01:01:29.001
this NFT saying to them.

01:01:29.001 --> 01:01:36.000
And I'm in New York City, in the New York
elected mayor, he just, I think it's

01:01:36.000 --> 01:01:40.000
yesterday he just announced he's going to
take his first repeat check in Bitcoin.

01:01:41.000 --> 01:01:46.001
And what we can do is I want to buy his
tweet as an FT. So I, I just, you know,

01:01:47.000 --> 01:01:53.001
go here and say, I will make an offer for
$1,000 for his tweet as an FT. So you

01:01:53.001 --> 01:01:56.001
can do many things you can
you can view this current web

01:01:56.001 --> 01:01:58.001
as an infrastructure layer.

01:01:58.001 --> 01:02:04.001
And do program on top. That's the key of
mass network. And this is a rep pocket

01:02:04.001 --> 01:02:11.000
to show NFT by the cell,
encrypted message, and your

01:02:11.000 --> 01:02:17.001
galleries, your digital footprint but
in a privacy preserved manner, your PNP

01:02:17.001 --> 01:02:24.001
NFTs, and also your tweets
become something you can own by

01:02:24.001 --> 01:02:29.000
yourself. Eventually, what we're trying
to try to argue and trying to do and

01:02:29.000 --> 01:02:36.000
trying to deliver is we view the,
the next generation of web, the D web is the

01:02:36.000 --> 01:02:37.001
value layer of the current web.

01:02:38.000 --> 01:02:42.001
And the current web, especially platforms
like Twitter and Facebook is becoming

01:02:42.001 --> 01:02:48.000
the
public utility is become the infrastructure.
It should not capture that value

01:02:48.000 --> 01:02:51.000
that much value we with
this they capture today.

01:02:51.000 --> 01:02:58.000
So let's build on top of them.
And without even let them permit, we just,

01:02:58.000 --> 01:03:01.000
you know, do something over top.

01:03:02.000 --> 01:03:08.000
We bring the D web on top of the web to
right now. Yeah, that's our goal. Yeah.

01:03:10.000 --> 01:03:12.000
Thank you. Thank you, Suji.

01:03:13.001 --> 01:03:19.000
I think this is the first project I've
seen that has this approach we've seen

01:03:19.000 --> 01:03:22.000
extensions working with web to.

01:03:22.001 --> 01:03:27.001
I'm just wondering if we have
time for one question. You and

01:03:27.001 --> 01:03:29.000
you see work in China.

01:03:30.000 --> 01:03:36.001
What do you think will happen when
you use mask on Weibo or Twitter.

01:03:37.000 --> 01:03:43.001
So the thing we tried to do is we
have to be decentralized. And I think

01:03:43.001 --> 01:03:50.000
the previous speaker, and also the audience
asked a question about the BDFL right

01:03:50.000 --> 01:03:51.001
the the open source with a king.

01:03:52.001 --> 01:03:58.000
In my opinion, I agree that we should make
quick decision on the iteration of the

01:03:58.000 --> 01:04:01.001
software but I think the key
I learned from the community.

01:04:02.001 --> 01:04:07.000
The activism community, journalism community
and you know, you see him on a big

01:04:07.000 --> 01:04:10.001
point is you should be headless. You should be

01:04:10.001 --> 01:04:12.000
headless so you don't need to worry about this.

01:04:12.000 --> 01:04:19.000
So let's say this Vitaly Buterin,
a Russian origin, a Canadian

01:04:19.000 --> 01:04:24.000
guy, raised some money in China and
mostly stay in Singapore sounds very

01:04:24.000 --> 01:04:28.000
suspicious and he's okay because
it's the Ethereum is headless.

01:04:28.001 --> 01:04:33.001
And obviously, I think a lot of other
projects survive and doing this like

01:04:33.001 --> 01:04:39.000
innovative way for decentralized web is
headless. So our goal is to be headless,

01:04:39.001 --> 01:04:42.000
which is, you know,
you can call me founder but I think it's CEO.

01:04:42.000 --> 01:04:48.001
It's not a proper title for next two years.
That's our goal. And then you can

01:04:48.001 --> 01:04:53.000
say, you can live whatever place you want.
You can be

01:04:53.000 --> 01:04:54.001
in the metaverse, you can be a nomad.

01:04:55.000 --> 01:04:59.001
But this thing is going to robust and
survive and grow itself. So that's

01:04:59.001 --> 01:05:02.000
also our goal and vision.

01:05:02.000 --> 01:05:08.000
Thank you. Thank you, Suji. I'm seeing
some good comments in the chat, including,

01:05:08.001 --> 01:05:15.000
yeah, including a conference that
Kalia Young is putting on about what's

01:05:15.000 --> 01:05:19.001
what comes after Facebook so want
to point everyone to that as well.

01:05:20.000 --> 01:05:27.000
Okay, well, from the metaverse where Suji,
who is not the founder but a

01:05:27.000 --> 01:05:34.000
contributor to mask.io is coming from
to Ottawa, Canada, where we want to

01:05:34.000 --> 01:05:39.000
bring you the words and the
insights of move signweaver.

01:05:39.000 --> 01:05:45.001
I know move in many different forms
he they they are Canadian tech

01:05:45.001 --> 01:05:51.001
enthusiasts with a passion
for decentralization I know
them as a contributor to

01:05:51.001 --> 01:05:56.000
the DAP protocol, you may know them
as one of the main people behind the

01:05:56.000 --> 01:06:02.001
Aggregore browser, but today move comes
to us to talk about hyper good dough.

01:06:03.000 --> 01:06:08.001
Hyper good dough is a new set of tools
that help you create peer to peer gaming

01:06:08.001 --> 01:06:15.001
using the good dough game engine.
So tell us more move signweaver.

01:06:17.001 --> 01:06:22.000
Hello, just get my slides up.
Can you hear me okay.

01:06:23.000 --> 01:06:28.001
Sweet. Hi, so I'm move. I'm a decentralized
software consultant, and today we're

01:06:28.001 --> 01:06:34.001
going to be using at looking, looking at
using D web technology in video games.

01:06:36.000 --> 01:06:40.001
So particularly we're going to be thinking
about multiplayer games. So a lot of

01:06:40.001 --> 01:06:45.000
games help connect folks together,
either through real time interactions like

01:06:45.000 --> 01:06:48.001
presence or sharing levels or
even just sharing high scores.

01:06:48.001 --> 01:06:53.000
And so this is usually accomplished by
game developers setting up a server

01:06:53.000 --> 01:06:55.001
somewhere in the cloud that
does all of that logic for you.

01:06:57.000 --> 01:07:02.001
However, cloud bad. Although the social
features we get from servers are nice.

01:07:03.000 --> 01:07:07.001
This comes with some downsides, particularly
developers now need to maintain back

01:07:07.001 --> 01:07:12.000
end infrastructure, which means you need
more specialized developers and you need

01:07:12.000 --> 01:07:15.000
more money to actually keep things working.

01:07:15.000 --> 01:07:20.001
As well, if servers go down or if a person's
internet is spotty then suddenly the

01:07:20.001 --> 01:07:25.000
game is completely useless and they can't
do anything with it. Similarly, if a

01:07:25.000 --> 01:07:31.001
company stops wanting to maintain these
servers, say like it's some sort of FPS

01:07:31.001 --> 01:07:33.001
that you might have enjoyed for a long time.

01:07:34.000 --> 01:07:38.001
The game becomes unplayable and whatever
community got built up around it really

01:07:38.001 --> 01:07:42.000
doesn't have much of a choice or
anything they can do about it.

01:07:43.001 --> 01:07:48.001
However, we can have all of the fun of
online multiplayer without the downsides

01:07:48.001 --> 01:07:51.001
of the cloud by using peer to peer software.

01:07:52.000 --> 01:07:56.001
So instead of connecting to a server
to send stuff like your avatar or your

01:07:56.001 --> 01:08:02.000
movement data or anything else that you
would normally use a server for it, you

01:08:02.000 --> 01:08:04.000
can instead connect directly
to other players and

01:08:04.000 --> 01:08:06.000
exchange it with peer to peer protocols.

01:08:06.001 --> 01:08:11.001
So this also means that developers don't
need to put as much effort into setting

01:08:11.001 --> 01:08:16.000
up the infrastructure. And even if development
stops the player base will be able

01:08:16.000 --> 01:08:21.001
to do everything that they're used
to as if nothing changed at all.

01:08:22.001 --> 01:08:27.000
So with that in mind, I've been working
on a set of tools called HyperGado. This

01:08:27.000 --> 01:08:32.001
combines the HyperCore protocol handlers
used in the Aggregore web browser with

01:08:32.001 --> 01:08:34.001
the open source Gado game engine.

01:08:35.000 --> 01:08:41.001
So HyperCore provides peer to peer data
transfer API, along with a way to send

01:08:41.001 --> 01:08:44.001
ephemeral messages over connections.

01:08:45.001 --> 01:08:51.001
And Gado is an easy to use game engine
with a really active community and it lets

01:08:51.001 --> 01:08:58.000
people create user interfaces 2D and 3D games,
all without needing to buy into

01:08:58.000 --> 01:09:01.001
proprietary software or
licenses like Unity or Unreal.

01:09:04.000 --> 01:09:10.001
So as well, we have a bunch of really
high level building blocks. So instead of

01:09:10.001 --> 01:09:14.000
developers having to figure out how to
do everything from scratch, they can use

01:09:14.000 --> 01:09:18.001
some of these primitives
from HyperGado to extend one

01:09:18.001 --> 01:09:20.000
of the high level demo scenes.

01:09:20.000 --> 01:09:26.001
So they can do common stuff like exchanging
player information, sending movement

01:09:26.001 --> 01:09:32.000
data on the peer to peer network,
and even stuff like using lobbies for finding

01:09:32.000 --> 01:09:35.001
games without having to have a
central server to track everything.

01:09:37.001 --> 01:09:42.000
So that's HyperGado.
I just wanted to give a really quick overview.

01:09:42.000 --> 01:09:47.001
I also wanted to quickly thank Stripe
Studios for funding this work and also

01:09:47.001 --> 01:09:50.001
wanted to give a big thanks
to Gado and their awesome

01:09:50.001 --> 01:09:52.000
documentation and community.

01:09:53.000 --> 01:09:58.000
And also thanks to the folks in the
Aggregore Discord that helped test some of

01:09:58.000 --> 01:10:02.001
this and actually see if this peer to
peer Gado stuff was actually viable.

01:10:02.001 --> 01:10:08.000
So if you want to learn more, I suggest
you either check out the GitHub repo and

01:10:08.000 --> 01:10:13.001
try to start a Gado project or
join us in the Aggregore Discord

01:10:13.001 --> 01:10:15.001
server and ask whatever questions.

01:10:17.000 --> 01:10:20.001
Yeah, so hopefully we have more time for Q&A.

01:10:21.001 --> 01:10:27.001
Thank you, Mo. There is a question.
If you're playing an FPS with a fairly large

01:10:27.001 --> 01:10:33.000
amount of movement data, is this movement
data all written to an append-only log?

01:10:33.001 --> 01:10:38.000
And how did you solve the multi-writer problem?

01:10:39.000 --> 01:10:45.000
Yeah, so the cool thing about movement
data is there's not that much benefit from

01:10:45.000 --> 01:10:51.000
having a history of movement.
So what we actually have in HyperGado is

01:10:51.000 --> 01:10:52.001
an ephemeral gossip layer.

01:10:52.001 --> 01:10:58.001
So the idea is you connect to people
in the level any which way or in an

01:10:58.001 --> 01:11:03.000
intelligent way, and you gossip out your
movement packets across the network.

01:11:03.001 --> 01:11:10.000
So if we have three people, A, B, and C,
A sends out a packet to B, B then

01:11:10.000 --> 01:11:14.001
rebroadcasts that to C. And instead of
having to track all of those downloads and

01:11:14.001 --> 01:11:18.001
all of that storage, it just kind of
spreads throughout the network, similar to

01:11:18.001 --> 01:11:21.000
how you would over the internet.

01:11:21.000 --> 01:11:27.000
So it kind of makes the load automatically
spread across the network, and you

01:11:27.000 --> 01:11:29.001
don't really take a penalty
for having a lot of history.

01:11:31.001 --> 01:11:36.000
Here's a question from Gareth. Does this
architecture make it easier to cheat in

01:11:36.000 --> 01:11:38.000
video games if everything is run client-side?

01:11:39.000 --> 01:11:46.000
Yeah, so the absolutely naive approach,
yes, it's super easy to cheat because if

01:11:46.000 --> 01:11:49.000
you just trust everything that comes
over the network, then anyone can do

01:11:49.000 --> 01:11:54.000
whatever you want. However, all you really
need to do is add a little bit of more

01:11:54.000 --> 01:11:56.000
validation.

01:11:56.000 --> 01:12:00.001
For instance, your client can detect
when somebody is like clipping through

01:12:00.001 --> 01:12:04.001
walls, and then you can collectively just
ban them rather than having a server

01:12:04.001 --> 01:12:08.000
detect that and also do something about it.

01:12:08.000 --> 01:12:12.001
As well, this really works for maybe
smaller scale things where you don't

01:12:12.001 --> 01:12:15.000
necessarily have like a global leaderboard

01:12:15.000 --> 01:12:16.001
where you're trying to
like show off to everyone.

01:12:17.001 --> 01:12:21.000
This is more like if you're making stuff
with friends, you can get away with

01:12:21.000 --> 01:12:22.001
making stuff easy to hack.

01:12:23.001 --> 01:12:28.001
But yeah, but the real answer is add
client-side validation if you want to

01:12:28.001 --> 01:12:33.001
prevent people from spoofing stuff.
And the bare minimum of that is to use

01:12:33.001 --> 01:12:36.001
encryption to actually verify that
data is coming from people that

01:12:36.001 --> 01:12:38.001
are allowed to send that data.

01:12:39.001 --> 01:12:43.001
So, Mo,
are you seeing anyone build with HyperGoTo yet?

01:12:44.001 --> 01:12:47.000
So, we're still super new.

01:12:48.000 --> 01:12:52.000
Olim been working for a few months
and we finally have like some core

01:12:52.000 --> 01:12:53.001
primitives to build on top.

01:12:55.000 --> 01:13:00.001
We don't have anyone using it yet,
but I'm hoping to reach out to some of the

01:13:00.001 --> 01:13:05.000
peer-to-peer, or sorry, decentralized VR
communities that are also building on

01:13:05.000 --> 01:13:10.000
Godot to see if we can do some sort of
partnerships so that we can make peer-to

01:13:10.000 --> 01:13:14.001
-peer virtual worlds together and load
them off of the D-Web, either in Godot or

01:13:14.001 --> 01:13:20.000
also by compiling Godot games to the
D-Web and say Aggregore, whatever

01:13:20.000 --> 01:13:21.001
other peer-to-peer browser.

01:13:22.001 --> 01:13:24.000
So no, but hopefully.

01:13:25.001 --> 01:13:29.001
Hopefully, by the time we have D-Web
camp in July, we can all be playing

01:13:29.001 --> 01:13:32.000
HyperGoTo in spirited game.

01:13:33.001 --> 01:13:34.001
Thanks so much, Mo.

01:13:35.001 --> 01:13:42.000
Okay, we are down to our last two lightning
talks. The next person to present

01:13:42.000 --> 01:13:48.000
is Joy Zhang.
Joy is the founder of Quark. She's a

01:13:48.000 --> 01:13:49.001
designer, she's an engineer.

01:13:49.001 --> 01:13:56.001
She's been a part of four different startups,
two of which she was the founder of

01:13:56.001 --> 01:14:01.001
today, though. She's here to talk about Quark,
which is a Web 3.0 browser plus

01:14:01.001 --> 01:14:07.000
social platform that shows you paths
across the internet. Joy, take it away.

01:14:08.001 --> 01:14:13.001
Thank you, Wendy. And hello, guys.
I'm pretty new to the D-Web community, so I'm

01:14:13.001 --> 01:14:19.000
really excited to be here. I'm going to
share my screen and we'll get started.

01:14:20.001 --> 01:14:26.001
Okay, so again, my name is Joy,
and today I'll be telling you about my startup

01:14:26.001 --> 01:14:31.000
Quark, which is a cross between
a browser and a social platform.

01:14:31.001 --> 01:14:36.000
And this is a bit strange, but really
with Quark, we asked one question related

01:14:36.000 --> 01:14:43.000
to expanding the reach of a democratic Web,
which is how do we incentivize the

01:14:43.000 --> 01:14:47.000
decentralized Web for online users at large,
especially people who

01:14:47.000 --> 01:14:48.001
aren't familiar with D-Web principles.

01:14:48.001 --> 01:14:54.000
To do that, we started with interaction
design and approached technology, a

01:14:54.000 --> 01:14:56.001
technology and policy problem
from a design perspective.

01:14:57.001 --> 01:15:03.000
And we found that the internet of today
is this entire universe with links

01:15:03.000 --> 01:15:07.001
emerging and dying off every single moment.
Each of us have our own unique

01:15:07.001 --> 01:15:09.000
constellations across it.

01:15:09.000 --> 01:15:15.001
And our complex browsing habits extend
into Web 2.0, Web 3.0, wherever

01:15:15.001 --> 01:15:17.000
we go within that universe.

01:15:18.000 --> 01:15:22.000
So it makes no sense that we're still
relying on technology based on the filing

01:15:22.000 --> 01:15:25.000
cabinet with tabs, folders and files.

01:15:26.000 --> 01:15:30.000
So Quark is the browser that shows
you paths across the internet.

01:15:30.000 --> 01:15:36.001
And those paths are indexed for the people
and by the people and are specifically

01:15:36.001 --> 01:15:41.000
made for explorers in the internet universe
like content creators and auto-idacs.

01:15:42.000 --> 01:15:46.000
So with Quark, we wanted to transform
going down a rabbit hole from something

01:15:46.000 --> 01:15:51.001
like this to an experience like this,
where you can see a collective map of the

01:15:51.001 --> 01:15:56.000
internet and where relationships between
websites are visually represented based

01:15:56.000 --> 01:15:59.000
off of recency, frequency and popularity.

01:16:00.000 --> 01:16:05.000
So how would we use Quark?
Let's look at one example where Quark makes

01:16:05.000 --> 01:16:09.000
information more accessible to a
content creator and also an auto-idac,

01:16:09.001 --> 01:16:11.001
doing research on sustainability.

01:16:11.001 --> 01:16:16.000
We're all trying our best to fight climate
change. For some of us, that means

01:16:16.000 --> 01:16:21.000
working on sustainability solutions such
as surlamps in and outside of work.

01:16:21.000 --> 01:16:26.001
There are thousands of people doing the
same thing all across the world. What if

01:16:26.001 --> 01:16:31.000
there's a way to share our expertise
based on shared purpose? With the browser

01:16:31.000 --> 01:16:33.000
Quark, there is a way.

01:16:33.001 --> 01:16:38.000
For example,
Neil is an expert in solar lamps who conducts

01:16:38.000 --> 01:16:39.001
most of his research online.

01:16:40.000 --> 01:16:45.000
As he goes online, the Quark browser
automatically organizes his online research.

01:16:45.001 --> 01:16:49.001
Neil is able to better track
and reaccess his own resources.

01:16:50.000 --> 01:16:55.000
When he's done, he can share his map of
resources to others in the world so that

01:16:55.000 --> 01:16:58.000
like-minded people can
discover helpful information.

01:16:59.000 --> 01:17:02.001
Now on the other side of the world,
Sally has just begun

01:17:02.001 --> 01:17:04.000
learning more about solar lamps.

01:17:05.000 --> 01:17:07.001
She begins using Quark to
learn from tagged resource

01:17:07.001 --> 01:17:09.000
maps from experts in the field.

01:17:09.000 --> 01:17:15.000
As she explores the content, the internet
path visualizations let her keep track

01:17:15.000 --> 01:17:19.000
of the larger picture and meet
others when viewing similar online

01:17:19.000 --> 01:17:21.000
websites and search results.

01:17:21.001 --> 01:17:27.000
She finds Neil and hitchhikes along with him,
discovering new resources together.

01:17:28.001 --> 01:17:32.000
Quark helps Sally and Neil
inspire each other and save

01:17:32.000 --> 01:17:33.001
energy on online searching.

01:17:33.001 --> 01:17:38.001
This is Quark, the browser that
shows you paths across the internet.

01:17:40.001 --> 01:17:44.001
So that shows you how two people
could possibly use Quark.

01:17:45.001 --> 01:17:49.000
But in Quark, what's important is that
the sharing and collectiveness is not

01:17:49.000 --> 01:17:51.000
forced, but rather intentional.

01:17:51.001 --> 01:17:56.000
So auto-didacs no longer have to start
from scratch when learning more about the

01:17:56.000 --> 01:17:58.001
D-Web, for example, or even solar lamps.

01:17:58.001 --> 01:18:03.000
And anyone can encounter like-minded
people right in the browser as you

01:18:03.000 --> 01:18:05.000
discover the content in real time.

01:18:05.001 --> 01:18:09.001
You also have full control of your online
constellations, whether you keep it to

01:18:09.001 --> 01:18:11.001
yourself or share it with the world.

01:18:12.001 --> 01:18:19.000
And to summarize, the idea is to enable
decentralized Googling and crowdsource

01:18:19.000 --> 01:18:23.000
content indexing, all while making the
browsing experience more suitable for

01:18:23.000 --> 01:18:26.001
niche content and recommendations
from other users.

01:18:26.001 --> 01:18:32.001
And it's the right time and place to build
this because 86% of Gen Z's trust read

01:18:32.001 --> 01:18:35.000
it now as much as Google or Amazon.

01:18:36.000 --> 01:18:40.001
And also hundreds of thousands of users
are already trying to work around for

01:18:40.001 --> 01:18:44.001
crowdsourcing content discovery on Twitch,
Twitter, Obsidian,

01:18:44.001 --> 01:18:46.000
Rome, and other extensions.

01:18:46.001 --> 01:18:51.000
And not many people are really looking
at the intersection of navigation

01:18:51.000 --> 01:18:55.001
experience and serendipity,
serendipitous connections between

01:18:55.001 --> 01:18:57.000
different pieces of information.

01:18:58.000 --> 01:19:02.000
There are no available tools that let
users discover, share, and keep track of

01:19:02.000 --> 01:19:06.000
content all in line with the browsing
experience, not to mention doing so

01:19:06.000 --> 01:19:08.000
locally or peer-to-peer.

01:19:08.000 --> 01:19:14.000
So we've had over 70 conversations and
interviews with heavy Internet users, all

01:19:14.000 --> 01:19:18.001
of whom have no connection to the D-Web
community, and there was a significant

01:19:18.001 --> 01:19:22.000
amount of interest for our
initial interface prototypes.

01:19:22.001 --> 01:19:25.001
So we're really, really early on,
much earlier than

01:19:25.001 --> 01:19:27.000
a lot of the projects we saw before.

01:19:27.001 --> 01:19:32.001
So we're currently developing an
MVP for a March beta release.

01:19:32.001 --> 01:19:38.001
Our team is pretty interdisciplinary
but comes at this problem from a design

01:19:38.001 --> 01:19:43.000
perspective and we really believe that if
this gets big, this could make a lot of

01:19:43.000 --> 01:19:48.001
those centralized platforms of today
look really archaic, and also less

01:19:48.001 --> 01:19:50.000
effective for finding what you want.

01:19:51.000 --> 01:19:57.000
So finally, I'm curious to hear what
you guys think. Do you think you'd use

01:19:57.000 --> 01:20:03.000
Quark? What do you think about the
platform so far, or what you saw? We're

01:20:03.000 --> 01:20:08.001
looking for beta testers and devs to take
equity-holding positions in the team or

01:20:08.001 --> 01:20:10.000
give any feedback about it.

01:20:11.000 --> 01:20:13.001
Anyhow,
thanks for your time and I hope to see you

01:20:13.001 --> 01:20:15.001
somewhere else on the Internet universe.

01:20:16.001 --> 01:20:23.000
Thank you so much, Joy.
People are asking, is there a URL

01:20:23.000 --> 01:20:25.000
where they can try out Quark?

01:20:26.000 --> 01:20:32.001
So right now there is an early interface,
but we're updating it currently, so the

01:20:32.001 --> 01:20:35.000
best way to get access is to fill out this

01:20:35.000 --> 01:20:36.001
interest form that I'm pasting in the chat.

01:20:37.000 --> 01:20:41.000
So we're going to be showing a few people
some prototypes to get feedback and

01:20:41.000 --> 01:20:43.001
hopefully develop it with input from users.

01:20:44.001 --> 01:20:48.000
People are saying they love that Quark
is kind of putting people into a virtual

01:20:48.000 --> 01:20:53.000
space across the web, a social layer
across the web that's really interesting.

01:20:53.001 --> 01:20:57.000
But does Quark support people
annotating web pages as part of

01:20:57.000 --> 01:20:58.001
that content that they're sharing?

01:20:59.001 --> 01:21:04.000
Yeah, so I've looked into a lot of
nonprofit organizations doing something

01:21:04.000 --> 01:21:07.001
similar,
like Hypothesis is actually one example.

01:21:08.000 --> 01:21:14.001
And interestingly enough, China is sort
of a leader in the space with messages

01:21:14.001 --> 01:21:17.000
that can be annotated by anyone using certain

01:21:17.000 --> 01:21:19.000
platforms, but it's all centralized.

01:21:19.001 --> 01:21:24.001
The idea is to enable annotation
because there's a lot of

01:21:24.001 --> 01:21:30.000
benefit and insight that can be brought
in just by seeing what other people

01:21:30.000 --> 01:21:31.001
think on a specific website.

01:21:34.000 --> 01:21:39.001
Great, great. So let's see.

01:21:41.000 --> 01:21:47.001
Want a colab to get P2P protocols into
your browser? Something like Aggregore?

01:21:48.000 --> 01:21:53.001
Yes, that would be so cool.
I actually messaged Mo on Twitter,

01:21:54.001 --> 01:21:58.000
but I thought I would be so down for that.

01:21:59.000 --> 01:22:04.000
We also know Dan Whaley, who's the founder
of Hypothesis, and he comes to a lot

01:22:04.000 --> 01:22:08.001
of D-Web events. So happy to make those
kind of introductions too, if you want

01:22:08.001 --> 01:22:10.000
to get deep into annotation.

01:22:10.001 --> 01:22:15.000
That would be amazing. Yeah, I found
them and I was like, how is someone else

01:22:15.000 --> 01:22:18.000
already doing this? Really pumped.

01:22:19.000 --> 01:22:23.000
Okay, well, Joy, thanks so much for sharing
and good luck. And we hope that you

01:22:23.000 --> 01:22:25.001
find some collaborators
right here in this group.

01:22:26.000 --> 01:22:28.000
Thank you, Wendy. And thank you, guys.

01:22:29.000 --> 01:22:35.001
Thank you. Okay, not least,
but last is our next presenter,

01:22:36.000 --> 01:22:42.000
Bernhard Borges. He's a PhD, so I suppose
we should call him Dr. Borges, coming

01:22:42.000 --> 01:22:45.000
to us from a city just north of Austin, Texas.

01:22:45.001 --> 01:22:50.000
He is a research scientist at the
Fluence Project, which is a peer-to-peer

01:22:50.000 --> 01:22:55.000
application platform that allows you to
create apps that are free of proprietary

01:22:55.000 --> 01:22:57.001
cloud providers or centralized APIs.

01:22:58.001 --> 01:23:03.000
He has a distinguished background.
Bernhard was a former chief scientist at Doc,

01:23:03.001 --> 01:23:08.001
a distinguished engineer at IBM,
and now he is the research scientist at Fluence

01:23:08.001 --> 01:23:10.001
Project. Bernhard, welcome to the D-Web.

01:23:11.001 --> 01:23:16.000
Thank you very much for having him.
Thanks for everybody for being here. Tough

01:23:16.000 --> 01:23:18.000
acts to follow. Great, great projects. This is

01:23:18.000 --> 01:23:20.000
awesome. Just listening in. Very nice.

01:23:22.000 --> 01:23:28.000
And just spend a little bit of time
explaining what Fluence does and how we think

01:23:28.000 --> 01:23:30.001
that with peer-to-peer protocols and networks,
we can

01:23:30.001 --> 01:23:32.000
change the centralized web narrative.

01:23:33.001 --> 01:23:40.001
And from our perspective, Web2 has been
an abject failure. We have never even

01:23:40.001 --> 01:23:44.000
come close to the division and admission
that's been put forward for the web.

01:23:45.000 --> 01:23:51.000
And the reality is actually brutal.
It is terrible. The more you look at it, the

01:23:51.000 --> 01:23:56.001
more depressed you get. Censorship,
not just from a traditional state-sponsored

01:23:56.001 --> 01:24:02.000
agency, but from a large variety
of corporations that use

01:24:02.000 --> 01:24:08.000
their business agreements
we all sign and never read,

01:24:09.000 --> 01:24:16.000
almost as weapons to make it very
difficult not just to onboard, but

01:24:16.000 --> 01:24:18.000
actually to stay onboard it and transact.

01:24:18.000 --> 01:24:24.001
We are relying on oligopoly of
cloud providers that have a very

01:24:24.001 --> 01:24:31.000
spotty performance record and as an
increasingly particular edge device based on

01:24:31.000 --> 01:24:38.000
social [...] cultures, even

01:24:38.000 --> 01:24:42.001
medical devices are dependent on internet
transactions, those kinds of brownouts

01:24:42.001 --> 01:24:45.000
are absolutely unacceptable.

01:24:45.001 --> 01:24:49.001
And then of course, nobody even talks about,
barely talks about anymore, that

01:24:49.001 --> 01:24:54.001
data breaches are, you know, you get your
$15 for your annual protection and

01:24:54.001 --> 01:24:56.001
that's pretty much all there is to it.

01:24:56.001 --> 01:25:02.000
Unless of course it gets further siloed
and sold drastically. So from our

01:25:02.000 --> 01:25:07.001
perspective, we really were looking at how
this can be changed from the bottom up

01:25:07.001 --> 01:25:14.000
and Fluence has been added for several years,
one of the earlier adopters, and we

01:25:14.000 --> 01:25:17.001
really feel that peer-to-peer protocols
and networks can improve a lot of the

01:25:17.001 --> 01:25:24.000
issues that put these chokeholds
into the Web 2 infrastructure and

01:25:24.000 --> 01:25:30.001
therefore we can start pushing into
Web 3 with a much more scalable and

01:25:30.001 --> 01:25:35.001
friendly environments that foster code
reuse because this is one of those

01:25:35.001 --> 01:25:42.000
problems still that further
mitigates access and democratizing

01:25:42.000 --> 01:25:46.000
the use of applications because the
code we use is actually fairly minimal.

01:25:47.000 --> 01:25:53.001
Despite many large providers,
including Amazon, for example, making an

01:25:53.001 --> 01:25:58.001
enormous amount of money, value capture
from open source contributions, and most

01:25:58.001 --> 01:26:02.001
of the projects actually benefit very,
very poorly from it.

01:26:02.001 --> 01:26:06.001
We also believe that security and
censorship resilience can be drastically

01:26:06.001 --> 01:26:11.001
improved with peer-to-peer networks and
we can really shift control of resources

01:26:11.001 --> 01:26:15.000
including data back to the user, to the owner.

01:26:16.000 --> 01:26:19.001
And that's sort of where Fluence comes in.
So what Fluence does is we have an

01:26:19.001 --> 01:26:26.000
open source peer-to-peer protocol that
allows the creation of applications free

01:26:26.000 --> 01:26:29.001
of a lot of centralized
intermediaries and centralized APIs.

01:26:29.001 --> 01:26:35.001
And the way it works is basically the
protocol is very compute-based and

01:26:35.001 --> 01:26:42.001
is represented then in nodes.
And the network we have, which is totally

01:26:42.001 --> 01:26:49.000
open and permissionless,
anybody can join, serves as a next-gen

01:26:49.000 --> 01:26:56.000
or decentralized cloud platform
that allows the deployment of

01:26:56.000 --> 01:27:02.001
custom services that can then be composed
with a language called Aqua into

01:27:02.001 --> 01:27:07.001
decentralized applications. So anybody
can run a node, peer-to-peer node that's

01:27:07.001 --> 01:27:14.000
based on libp2p, join the network and
start providing compute capabilities. On

01:27:14.000 --> 01:27:20.000
those compute capabilities through WebAssembly,
services can be deployed and they

01:27:20.000 --> 01:27:24.000
can then be through a marketplace even
discovered, they can be free, they can be

01:27:24.000 --> 01:27:28.001
chart for whatever it needs to be and
can then be composed with our language

01:27:28.001 --> 01:27:33.001
called Aqua, which is very, very high level.
So it really abstracts away from all

01:27:33.001 --> 01:27:37.000
the problems you usually find when you have to

01:27:37.000 --> 01:27:39.000
program in the peer-to-peer environment.

01:27:40.000 --> 01:27:44.000
And I probably should have brought an example,
but I didn't because I knew time

01:27:44.000 --> 01:27:49.001
was tight. And it's almost, it's not
quite as easy as content addressability

01:27:49.001 --> 01:27:55.000
provided by IPFS, but it's very close.
We're basically operating off-location

01:27:55.000 --> 01:27:58.001
tuples instead of single CID,
but it's very similar.

01:27:58.001 --> 01:28:05.001
And provide a lot of integration with
decentralized web protocols, including IPFS

01:28:05.001 --> 01:28:11.001
and IPFS related solutions such as ceramic,
textile, etc,

01:28:12.000 --> 01:28:13.001
blockchains and many more.

01:28:14.000 --> 01:28:20.001
And one of the core tenets of the Fluence
network is the data model. The data

01:28:20.001 --> 01:28:24.001
model is a push model. Unlike in the
traditional cloud server where you make a

01:28:24.001 --> 01:28:27.001
call and get a response back,
you make a call, you get a response back.

01:28:28.001 --> 01:28:35.001
In our peer-to-peer world,
we have a data push model. So unless the

01:28:35.001 --> 01:28:40.001
workflow seizes or there is a reason for
co-routine to come back to the client,

01:28:41.000 --> 01:28:44.001
all the computation is pushed
out to the network, which

01:28:44.001 --> 01:28:46.000
makes for very, very thin clients.

01:28:46.000 --> 01:28:51.001
I mean, much thinner than just browsers
and edge devices. And since the majority

01:28:51.001 --> 01:28:58.001
of the 8 billion people out there do not have
$5,000 MacBook Pros or $1,500 Apple

01:28:58.001 --> 01:29:04.001
iPhones, but run on much lower hardware,
thin clients are, in our opinion, a

01:29:04.001 --> 01:29:10.000
huge,
huge requirement in order to democratize and

01:29:10.000 --> 01:29:12.001
access to a lot of resources.

01:29:12.001 --> 01:29:16.001
And that we believe with
peer-to-peer we can do.

01:29:18.001 --> 01:29:23.001
If I have, I haven't heard the clock yet,
but this sort of how it looks like from

01:29:23.001 --> 01:29:28.001
a technology perspective, there are two
layers to Fluence. One is marine, which

01:29:28.001 --> 01:29:33.000
is basically everything that needs
to be done in order to manage

01:29:33.000 --> 01:29:34.001
distributed computation.

01:29:34.001 --> 01:29:41.001
And all these distributed services
are based on WebAssembly IT.

01:29:42.001 --> 01:29:49.000
So very, very portable, very next gen,
very relatively easy to

01:29:49.000 --> 01:29:55.000
do and a great alternative to your average

01:29:55.000 --> 01:29:56.001
function as a service.

01:29:56.001 --> 01:30:02.000
And then the Aqua language I mentioned
before is really a composition language

01:30:02.000 --> 01:30:05.001
that allows you to script distributed systems,
including peer-to-peer

01:30:05.001 --> 01:30:11.000
application, and that actually goes past
the boundaries of the Fluence network.

01:30:11.001 --> 01:30:16.001
And we have integrations with IPFS,
for example, where you can use, where you can

01:30:16.001 --> 01:30:21.000
compose,
compute and store with IPFS using Aqua.

01:30:21.001 --> 01:30:26.000
So that was sort of it in a nutshell.
If you want to learn more, Fluence.network,

01:30:27.000 --> 01:30:32.001
GitHub, it's github.com forward slash
Fluence Labs. We're on any of the channels,

01:30:33.000 --> 01:30:35.000
Discord, Telegram, Twitter,
Fluence, blah, blah, blah.

01:30:36.000 --> 01:30:39.001
If you want to go Discord,
that's probably where a lot of the developments

01:30:39.001 --> 01:30:41.000
happening. It's fluence.chat.

01:30:42.000 --> 01:30:46.001
And like everybody else we're hiring,
if you're in the decentralized web, if

01:30:46.001 --> 01:30:51.000
you're interested, technology or on the
operations side, shout out and we'd

01:30:51.000 --> 01:30:53.000
love to talk to you.

01:30:54.000 --> 01:30:56.000
Anybody have any questions? I'm ready.

01:30:56.000 --> 01:31:03.000
I think you had to double quack,
Bernard, but I hope that you'll come

01:31:03.000 --> 01:31:09.001
over to join us and gather and also come
back next month when you can have a

01:31:09.001 --> 01:31:13.000
booth and people can come up
and find you and learn more.

01:31:13.001 --> 01:31:15.001
But thank you so much for joining us.

01:31:16.001 --> 01:31:23.000
Okay, well that was a lot to take in.
We've basically gone around the world. And

01:31:23.000 --> 01:31:29.000
I just wanted to say thanks and remind
you that next month we're going

01:31:29.000 --> 01:31:30.001
to do something just a little bit different.

01:31:30.001 --> 01:31:36.001
We're going to do a holiday fair inspired
by a trip I took to Berlin where you

01:31:36.001 --> 01:31:38.001
have all these wonderful holiday booths.

01:31:38.001 --> 01:31:42.000
And each of you can have a booth and
people will come up and ask you about your

01:31:42.000 --> 01:31:48.000
projects, you can see if they're looking
for jobs, looking for volunteers, and

01:31:48.000 --> 01:31:52.001
all you have to do is fill out this Jot form,
which will drop into the chat and

01:31:52.001 --> 01:31:57.000
claim a booth and gather town. We hope no
matter what you'll come and party with

01:31:57.000 --> 01:32:02.001
us for the holidays.
That's December 8 at 10am Pacific.

01:32:03.001 --> 01:32:08.001
And finally, this is what we always do
some people will stay for hours and want

01:32:08.001 --> 01:32:14.000
to send you over to our environment at gather.
town I don't know if you guys have

01:32:14.000 --> 01:32:17.000
ever been there when we started with
gather town, there were like three

01:32:17.000 --> 01:32:23.000
engineers, they just, I think, raised
$50 million yesterday in their

01:32:23.000 --> 01:32:30.000
latest round of VC funding. But this is
what it'll look like you'll be in a park,

01:32:30.000 --> 01:32:32.001
you'll have an avatar you can run
around you can ask people to come [...]

01:32:32.001 --> 01:32:36.000
You can ask people questions, you can
put a cone of silence around you in case

01:32:36.000 --> 01:32:40.001
you want to have a private conversation.
There's lots of fun functionalities. So

01:32:40.001 --> 01:32:43.000
please, we're dropping this into the chat.

01:32:43.001 --> 01:32:49.001
The password is get D web. And thank you
so much for being with us. We really

01:32:49.001 --> 01:32:55.000
love seeing everyone and thank you so
much Coraline for your inspiring words.

01:32:56.000 --> 01:32:58.000
Okay, take care and we'll see you next month.

01:32:58.000 --> 01:32:59.000
In gather.